Triple
T4163195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U3 |
E91577
|
entity |
| Predicate | hasExtensionOpening |
P23994
|
FINISHED |
| Object | 2011-12-10 |
—
|
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: 2011-12-10 | Statement: [U3, hasExtensionOpening, 2011-12-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExtensionOpening Context triple: [U3, hasExtensionOpening, 2011-12-10]
-
A.
hasOpeningType
Indicates that one entity has, features, or is characterized by a particular type or kind of opening.
-
B.
extensionOpened
chosen
Indicates that a software extension has been activated or launched from its previously closed or inactive state.
-
C.
hasOpeningFeature
Indicates that an entity possesses a specific characteristic, element, or attribute related to its opening or entry point.
-
D.
isOpenTo
Indicates that one entity is receptive, willing, or available to consider, accept, or engage with another entity or proposal.
-
E.
hasOpeningDeclaredBy
Indicates that the opening or initial state of something is formally specified or announced by a particular agent or authority.
- 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_69aed9626ebc8190a39de631788bea3e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.