Triple
T26493890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Order 191 |
E669227
|
entity |
| Predicate | orderedOccupationOf |
P166152
|
FINISHED |
| Object | Hagerstown, Maryland |
—
|
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: Hagerstown, Maryland | Statement: [Special Order 191, orderedOccupationOf, Hagerstown, Maryland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderedOccupationOf Context triple: [Special Order 191, orderedOccupationOf, Hagerstown, Maryland]
-
A.
endedOccupationOf
Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
-
B.
allowedOccupationOf
Indicates that one entity is permitted or authorized to hold or perform the occupation associated with another entity.
-
C.
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).
-
D.
occupiedFrom
Indicates that an entity is in use or inhabited starting from a specified point in time.
-
E.
occupationOf
Indicates that one entity holds or performs the job, role, or profession associated with 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 27, 2026, 1:06 a.m.