Triple
T8470175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X3 |
E200259
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | ASC X3 |
E200259
|
NE 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: ASC X3 | Statement: [X3, alsoKnownAs, ASC X3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ASC X3 Context triple: [X3, alsoKnownAs, ASC X3]
-
A.
X-32
X-32 is an experimental Boeing-built prototype fighter aircraft developed for the Joint Strike Fighter competition.
-
B.
X3
chosen
X3 is the former designation of the standards body now known as INCITS, which oversees information technology standards in the United States.
-
C.
X-333
X-333 is a major process building at the Portsmouth Gaseous Diffusion Plant used in the large-scale enrichment of uranium.
-
D.
XR-7
XR-7 is a higher-end, performance-oriented trim package of the Mercury Cougar that added luxury and sporty features beyond the base model.
-
E.
Sharp X1
The Sharp X1 is a series of 8-bit home computers released by Sharp Corporation in the early 1980s, known for their advanced graphics and sound capabilities in the Japanese market.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f234c481909534de6fd702f4cf |
completed | March 31, 2026, 3:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce39f45c3081908ea50810f0a386d6 |
completed | April 2, 2026, 9:42 a.m. |
Created at: March 30, 2026, 6:11 p.m.