Triple
T280225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Board of Selectmen |
E5336
|
entity |
| Predicate | isHeadedBy |
P981
|
FINISHED |
| Object | chairperson |
—
|
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: chairperson | Statement: [Board of Selectmen, isHeadedBy, chairperson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHeadedBy Context triple: [Board of Selectmen, isHeadedBy, chairperson]
-
A.
isHeadOf
Indicates that one entity holds the leading or principal authority position over another entity, such as an organization, group, or department.
-
B.
hasLeader
chosen
Indicates that one entity serves as the leader or head of another entity.
-
C.
hasChiefExecutiveRole
Indicates that an entity holds the highest executive leadership position and overall managerial authority within an organization.
-
D.
headOfOrder
Indicates that one entity holds the primary leadership or highest authority position within a particular order or organized group.
-
E.
headOfGovernmentBody
Indicates that one entity serves as the chief executive or leading official in charge of governing another entity, typically a political or administrative body.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e0868708190ad551ca06cc57f4a |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b765f488190b2cbe4b45cd42821 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.