Triple
T18875889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Wells |
E461683
|
entity |
| Predicate | plansHeistOf |
P126716
|
FINISHED |
| Object | antique French scepter |
—
|
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: antique French scepter | Statement: [Nick Wells, plansHeistOf, antique French scepter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plansHeistOf Context triple: [Nick Wells, plansHeistOf, antique French scepter]
-
A.
plansRobberyIn
chosen
Indicates that an entity is preparing or organizing to commit a robbery within a specified location or jurisdiction.
-
B.
plan
Indicates that an entity intends or arranges for a future action or sequence of actions to occur.
-
C.
plansKidnappingOf
Indicates that one entity is formulating or organizing a plan to abduct another entity against their will.
-
D.
plannedAttack
Indicates that an entity has intentionally prepared and organized an attack against a target.
-
E.
plannedVia
Indicates that something is arranged, organized, or scheduled by means of a particular method, process, or intermediary.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3ce07788190a179705eb1b6c824 |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e48d22dde8819093b1d963bd673365 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.