Triple
T30709529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town government of Concord, Massachusetts |
E781852
|
entity |
| Predicate | usesTitleForExecutiveHead |
P36552
|
FINISHED |
| Object | Town Manager |
—
|
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: Town Manager | Statement: [Town government of Concord, Massachusetts, usesTitleForExecutiveHead, Town Manager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTitleForExecutiveHead Context triple: [Town government of Concord, Massachusetts, usesTitleForExecutiveHead, Town Manager]
-
A.
hasExecutiveHeadTitle
chosen
Indicates the official job title held by the person who serves as the executive head of an organization or entity.
-
B.
officeHolderMayUseTitle
Indicates that a person who holds a particular office is permitted to use a specified official title.
-
C.
usesTitleIn
Indicates that an entity is referred to using a particular title within a specified context or medium.
-
D.
hasChiefTitle
Indicates that an entity holds or is associated with a specific chief-level title or designation within an organization or group.
-
E.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 29, 2026, 8:35 p.m.