Triple
T16694677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windsor Herald of Arms in Ordinary |
E405682
|
entity |
| Predicate | permanentPosition |
P124274
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Windsor Herald of Arms in Ordinary, permanentPosition, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentPosition Context triple: [Windsor Herald of Arms in Ordinary, permanentPosition, true]
-
A.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
B.
positionEstablishedIn
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
-
C.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
-
D.
positionSpecific
Indicates that something applies only at, or is defined with respect to, a particular position or location within a larger structure or sequence.
-
E.
primaryPosition
Indicates the main role, job, or position an entity holds among potentially multiple positions.
- F. None of above. chosen
Provenance (4 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37eacfa788190a8d2058f96c0d445 |
completed | April 18, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:19 a.m.