Triple
T28860119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Texas Giant |
E728835
|
entity |
| Predicate | openedAsNewVersionOf |
P23567
|
FINISHED |
| Object | Texas Giant in 2011 |
—
|
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: Texas Giant in 2011 | Statement: [New Texas Giant, openedAsNewVersionOf, Texas Giant in 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsNewVersionOf Context triple: [New Texas Giant, openedAsNewVersionOf, Texas Giant in 2011]
-
A.
openedAsUpgradeOf
chosen
Indicates that one entity was opened specifically as an upgraded or improved replacement of another entity.
-
B.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
C.
openedAsBranchOf
Indicates that one entity was established and began operating as a branch or subsidiary location of another entity.
-
D.
containsNewVersionOf
Indicates that one entity includes or embeds a newer version of another entity.
-
E.
openedWith
Indicates that an entity is opened, initiated, or accessed using a specified tool, method, or instrument.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 28, 2026, 6:46 a.m.