Triple
T34896501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicolas Cage as Castor Troy |
E1006448
|
entity |
| Predicate | plansAct |
P14398
|
FINISHED |
| Object | bombing in Los Angeles |
—
|
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: bombing in Los Angeles | Statement: [Nicolas Cage as Castor Troy, plansAct, bombing in Los Angeles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plansAct Context triple: [Nicolas Cage as Castor Troy, plansAct, bombing in Los Angeles]
-
A.
plan
chosen
Indicates that an entity intends or arranges for a future action or sequence of actions to occur.
-
B.
proposedLaw
Indicates that an entity has formally put forward a law or legislative measure for consideration or approval.
-
C.
legislativeActOf
Indicates a relationship where a legislative act is authored, enacted, or formally issued by a specific legislative body or authority.
-
D.
politicalAct
Indicates that an entity performs, participates in, or is involved with an action related to politics, governance, or public policy.
-
E.
planning
Indicates that an entity is engaged in organizing or devising a future action, event, or course of behavior involving another entity or entities.
- 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.