Triple
T6627237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hero of Bennington |
E149833
|
entity |
| Predicate | hasOccupationOfDesignee |
P71831
|
FINISHED |
| Object | general |
—
|
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: general | Statement: [Hero of Bennington, hasOccupationOfDesignee, general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOccupationOfDesignee Context triple: [Hero of Bennington, hasOccupationOfDesignee, general]
-
A.
endedOccupationOf
Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
-
B.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
C.
occupationDuringAlias
Indicates that an entity held a particular occupation specifically during the time period when it was known by a given alias.
-
D.
requiredOccupationOf
Indicates that one entity specifies the occupation or job role that is required or expected for another entity (such as a position, task, or qualification).
-
E.
isAssociatedWithProfessionOfBearer
Indicates that one entity is connected to, or involved with, the profession or occupational role held by another entity.
- 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_69c687ee50048190aa151765bef16193 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c308a08881908501c862b3029321 |
completed | March 27, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c6ad024860819084b9b535b136ede6 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6c30733908190980f7ffaa5c5527b |
completed | March 27, 2026, 5:48 p.m. |
Created at: March 27, 2026, 1:59 p.m.