Triple
T19114205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hearst Doubles Match |
E467863
|
entity |
| Predicate | courseOfFire |
P134476
|
FINISHED |
| Object | rapid fire stages |
—
|
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: rapid fire stages | Statement: [Hearst Doubles Match, courseOfFire, rapid fire stages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courseOfFire Context triple: [Hearst Doubles Match, courseOfFire, rapid fire stages]
-
A.
firingControl
Indicates a relationship where one entity directs, regulates, or initiates the firing or discharge action of another entity or system.
-
B.
numberOfShotsFired
Indicates the total count of shots that were discharged in the described event or action.
-
C.
fireControlSystem
Indicates a relationship where a system monitors, directs, and coordinates the detection, targeting, and firing of weapons or other actuators to control the application of force or energy.
-
D.
firingPlatform
Indicates a platform or structure from which a weapon or projectile is launched or fired.
-
E.
underFire
Indicates that an entity is being attacked, heavily criticized, or subjected to intense pressure by another entity or group.
- 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_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. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:05 p.m.