Triple
T27343371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challenger (OV-099) |
E684168
|
entity |
| Predicate | constructionOrigin |
P168592
|
FINISHED |
| Object | Structural Test Article STA-099 |
—
|
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: Structural Test Article STA-099 | Statement: [Challenger (OV-099), constructionOrigin, Structural Test Article STA-099]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionOrigin Context triple: [Challenger (OV-099), constructionOrigin, Structural Test Article STA-099]
-
A.
constructionCompanyOrigin
Indicates that a construction company originates from, or is based in, a particular geographic location or jurisdiction.
-
B.
constructionBase
Indicates that one entity serves as the foundational structure or base upon which another entity is constructed or built.
-
C.
constructionUsed
Indicates that one entity was employed as a construction method, material, or component in creating or assembling another entity.
-
D.
architectOrigin
Indicates that an architect originally comes from, or is associated with, a particular place or region.
-
E.
constructionType
Indicates the specific method or style by which something is built or constructed.
- F. None of above. chosen
Provenance (4 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 27, 2026, 11:44 a.m.