Triple
T38024175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weapon XI |
E948721
|
entity |
| Predicate | projectDesignation |
P189969
|
FINISHED |
| Object | Weapon XI |
—
|
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: Weapon XI | Statement: [Weapon XI, projectDesignation, Weapon XI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectDesignation Context triple: [Weapon XI, projectDesignation, Weapon XI]
-
A.
projectionDesignBy
Indicates that a projection or projected visual element is created or designed by a particular agent or designer.
-
B.
exportDesignation
Indicates that something is assigned a specific status or classification for export-related purposes, such as regulatory, legal, or logistical handling.
-
C.
programDesignation
Indicates that an entity is assigned or identified by a specific program designation or label.
-
D.
bdDesignation
Indicates that one entity is formally assigned or designated as having a particular role, status, or classification in relation to another entity.
-
E.
exampleDesignation
Indicates that one entity is identified or labeled as a representative or illustrative instance of another entity.
- 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fc4747b06c8190a3ea5331f02eedad |
completed | May 7, 2026, 8:03 a.m. |
Created at: May 3, 2026, 4:20 p.m.