Triple
T35676449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HP |
E1030872
|
entity |
| Predicate | operatorCommencedOperationsYear |
P80913
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [HP, operatorCommencedOperationsYear, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorCommencedOperationsYear Context triple: [HP, operatorCommencedOperationsYear, 1983]
-
A.
operatedInYear
Indicates that an entity was actively operating or functioning during a specified year.
-
B.
operatedYearRound
Indicates that the subject entity functioned or was in operation continuously throughout the entire year, without seasonal closure.
-
C.
operatedSince
chosen
Indicates that an entity has been in operation continuously from a specified starting time or date.
-
D.
operatedDuring
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
E.
operatedFor
Indicates that one entity performed operations or provided services on behalf of, or in support of, another entity for a certain period or purpose.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0174142430819084aa1235500b9d3b |
completed | May 11, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_6a0171a6e0088190958679bb6cb24a70 |
completed | May 11, 2026, 6:05 a.m. |
Created at: May 3, 2026, 4:05 p.m.