Triple
T19114241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NTIT (Rattle Battle) |
E467864
|
entity |
| Predicate | firingDistances |
P128887
|
FINISHED |
| Object | 600 yards |
—
|
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: 600 yards | Statement: [NTIT (Rattle Battle), firingDistances, 600 yards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firingDistances Context triple: [NTIT (Rattle Battle), firingDistances, 600 yards]
-
A.
firingDirection
Indicates the direction or trajectory along which a firing action (such as shooting or launching a projectile) is aimed or executed.
-
B.
shootingRange
Indicates that one entity serves as a location or facility where another entity engages in shooting activities, typically for practice or training.
-
C.
numberOfShotsFired
Indicates the total count of shots that were discharged in the described event or action.
-
D.
artilleryRange
chosen
Indicates that one entity is within the effective firing distance of another entity’s artillery.
-
E.
firingControl
Indicates a relationship where one entity directs, regulates, or initiates the firing or discharge action of another entity or 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e39617408190b5134918f54f9c52 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.