Triple
T149889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challenger 2 |
E3407
|
entity |
| Predicate | originIndustry |
P71
|
FINISHED |
| Object | British defence industry |
—
|
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: British defence industry | Statement: [Challenger 2, originIndustry, British defence industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originIndustry Context triple: [Challenger 2, originIndustry, British defence industry]
-
A.
countryOfOrigin
Indicates the country from which an entity originally comes or was first produced, created, or established.
-
B.
sector
chosen
Indicates that an entity operates in, belongs to, or is associated with a particular economic or industrial sector.
-
C.
hasHistoricIndustry
Indicates that an entity has been associated with a notable or historically significant industry or industrial activity in the past.
-
D.
placeOfOrigin
Indicates the location or source from which an entity originally comes or was created.
-
E.
economicClassification
Indicates how an entity is categorized based on its economic characteristics, status, or role within an economic system.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a256599db08190a7b000b381d32ec4 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.