Triple
T7497694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flint Marko |
E177174
|
entity |
| Predicate | originOfPowers |
P61281
|
FINISHED |
| Object | particle accelerator accident |
—
|
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: particle accelerator accident | Statement: [Flint Marko, originOfPowers, particle accelerator accident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originOfPowers Context triple: [Flint Marko, originOfPowers, particle accelerator accident]
-
A.
legislativePowersDerivedFrom
Indicates that an entity’s authority to make or enact laws originates from, or is granted by, another specified source.
-
B.
sourceOfPower
chosen
Indicates that one entity serves as the origin or provider of power, energy, or authority for another entity.
-
C.
monarchPowers
Indicates the formal authorities, rights, and prerogatives legally or traditionally held by a monarch over their realm or subjects.
-
D.
kingPowers
Indicates that an entity possesses the legal or authoritative powers associated with a king over another entity or domain.
-
E.
scopeOfPower
Indicates the range or extent of authority, control, or decision-making power that an entity is permitted to exercise.
- 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_69c69f2696688190915a8458f2398211 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81b431481908214b69c6c8d83bc |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d266d88190982cf5d2ee2e9564 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:44 p.m.