Triple
T8260682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conventional Armed Forces in Europe Treaty |
E193183
|
entity |
| Predicate | limitsCategory |
P81548
|
FINISHED |
| Object | battle tanks |
—
|
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: battle tanks | Statement: [Conventional Armed Forces in Europe Treaty, limitsCategory, battle tanks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitsCategory Context triple: [Conventional Armed Forces in Europe Treaty, limitsCategory, battle tanks]
-
A.
limitsOffice
Indicates that one entity imposes a restriction or cap on the scope, duration, or powers of another entity’s office or official position.
-
B.
listedBuildingCategory
Indicates the heritage protection grade or category assigned to a building that is officially recognized as a listed structure.
-
C.
safetyCategory
Indicates the classification of something according to its level or type of safety.
-
D.
categoryLabel_H
Indicates that an entity is assigned a human-readable category label or classification.
-
E.
commonsCategory
Indicates that an entity is associated with a specific media or topic category on Wikimedia Commons.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7936b72c8190b998da033df611d1 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4ab5162c8190bddd696078689895 |
completed | March 31, 2026, 4:16 a.m. |
Created at: March 30, 2026, 5:49 p.m.