Triple
T26973872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alwinton |
E679393
|
entity |
| Predicate | isAtHeadOf |
P161403
|
FINISHED |
| Object | Coquet Valley |
—
|
NE NERFINISHED |
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: Coquet Valley | Statement: [Alwinton, isAtHeadOf, Coquet Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAtHeadOf Context triple: [Alwinton, isAtHeadOf, Coquet Valley]
-
A.
isHeadOf
Indicates that one entity holds the leading or principal authority position over another entity, such as an organization, group, or department.
-
B.
hasHeadOf
Indicates that one entity serves as the leader, chief, or person in charge of another entity (such as an organization, group, or department).
-
C.
mayBeHeadedBy
Indicates that an entity can potentially serve as the leader or head of another entity, but this leadership is not certain or currently established.
-
D.
tookHeadOf
Indicates that one entity removed or claimed the head (literal or symbolic) of another entity.
-
E.
headOfOrder
Indicates that one entity holds the primary leadership or highest authority position within a particular order or organized group.
- 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6212682488190bcf8ff6a98296bdf |
completed | May 2, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 6:41 a.m.