Triple
T7756245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron von Steingel |
E175902
|
entity |
| Predicate | commissionedStructureType |
P3145
|
FINISHED |
| Object | castle |
—
|
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: castle | Statement: [Baron von Steingel, commissionedStructureType, castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissionedStructureType Context triple: [Baron von Steingel, commissionedStructureType, castle]
-
A.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
B.
commissionedUnit
Indicates that one entity formally authorizes or assigns another entity (the commissioned unit) to carry out a specific task, role, or function.
-
C.
commissioned
chosen
Indicates that one entity formally authorized or ordered another entity to create, produce, or carry out something, often in exchange for payment or obligation.
-
D.
commissionedStatus
Indicates whether an entity has been formally authorized, activated, or placed into official service or duty.
-
E.
builtStructureFor
Indicates that one entity constructed or assembled a structure specifically intended for the use, benefit, or purpose of another entity.
- 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_69c6996180088190832e38e8d83ff54a |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c705257ca08190a78c592a1e616da8 |
completed | March 27, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69c7016df2b08190b2330a2010691431 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:08 p.m.