Triple
T25186701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NX-01 |
E630736
|
entity |
| Predicate | predecessorInNaming |
P39756
|
FINISHED |
| Object | Enterprise (XCV 330) |
—
|
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: Enterprise (XCV 330) | Statement: [NX-01, predecessorInNaming, Enterprise (XCV 330)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorInNaming Context triple: [NX-01, predecessorInNaming, Enterprise (XCV 330)]
-
A.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
B.
predecessorNameUsage
chosen
Indicates that a name was used previously and has been replaced or superseded by a subsequent name in a sequence or lineage.
-
C.
predecessorNameForm
Indicates that the value is a name or naming form previously used for the same entity before its current name.
-
D.
predecessorInRole
Indicates that one entity previously held a particular role or position that was later occupied by another entity.
-
E.
predecessorLocatedAt
Indicates that the location specified was the place where the immediately preceding version, state, or instance of an entity was situated.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 12:44 p.m.