Triple
T38572113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act I: The royal birthday and crossbow gift |
E929302
|
entity |
| Predicate | hasMainProp |
P23698
|
FINISHED |
| Object | crossbow |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: crossbow | Statement: [Act I: The royal birthday and crossbow gift, hasMainProp, crossbow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainProp Context triple: [Act I: The royal birthday and crossbow gift, hasMainProp, crossbow]
-
A.
hasMainKey
Indicates that an entity possesses or is associated with a primary or principal key used for identification or access.
-
B.
hasMainSymbol
Indicates that one entity is designated as the primary or most representative symbol associated with another entity.
-
C.
hasMainStructure
Indicates that one entity serves as the primary or central structural component of another entity.
-
D.
hasMainElements
Indicates that something possesses or is composed of its primary or most important constituent parts.
-
E.
haveProperty
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.