Triple
T3879629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbian cross |
E92787
|
entity |
| Predicate | firesteelsPosition |
P52105
|
FINISHED |
| Object | one firesteel in each quadrant of the cross |
—
|
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: one firesteel in each quadrant of the cross | Statement: [Serbian cross, firesteelsPosition, one firesteel in each quadrant of the cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firesteelsPosition Context triple: [Serbian cross, firesteelsPosition, one firesteel in each quadrant of the cross]
-
A.
fireModes
Indicates the different ways or settings in which a weapon or device can be fired or operated.
-
B.
selectFire
Indicates choosing or designating a specific fire source, mode, or target for use or activation.
-
C.
fireSupportType
Indicates the specific kind or category of supporting fire (such as artillery, air support, or naval gunfire) being provided in a military context.
-
D.
fires
Indicates that an agent initiates the discharge or ignition of something, such as a weapon, engine, or explosive device, causing it to operate or go off.
-
E.
notableFire
Indicates that a significant or historically important fire event is associated with the subject.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7574c408190893e70bf80514838 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef14f9bb4819098e64b527b546d74 |
completed | March 9, 2026, 4:11 p.m. |
Created at: March 9, 2026, 3:20 p.m.