Triple
T27970418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GOV |
E706338
|
entity |
| Predicate | positionTypeIndicated |
P112307
|
FINISHED |
| Object | Governor of an institution |
—
|
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: Governor of an institution | Statement: [GOV, positionTypeIndicated, Governor of an institution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionTypeIndicated Context triple: [GOV, positionTypeIndicated, Governor of an institution]
-
A.
positionRepresented
Indicates that one entity serves as a representation or proxy for a particular position, role, or office held by another entity.
-
B.
typicalPositionType
chosen
Indicates the usual or most common positional role or placement type that an entity generally occupies or is associated with.
-
C.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
D.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
E.
positionOften
Indicates that one entity frequently holds, occupies, or is located at a particular position relative to another entity or context.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 27, 2026, 7:37 p.m.