Triple
T23512691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Barron |
E572468
|
entity |
| Predicate | claimedInjuryFrom |
P14656
|
FINISHED |
| Object | city public works projects |
—
|
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: city public works projects | Statement: [John Barron, claimedInjuryFrom, city public works projects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedInjuryFrom Context triple: [John Barron, claimedInjuryFrom, city public works projects]
-
A.
allegedInjury
Indicates that an injury is claimed or asserted to have occurred, typically without being legally or factually established.
-
B.
causeOfInjury
chosen
Indicates that one entity is the source or reason that another entity sustained an injury.
-
C.
causeOfClaim
Indicates the underlying reason, event, or condition that gives rise to a particular claim.
-
D.
injuredIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or action.
-
E.
typeOfClaim
Indicates the specific category or nature of a claim being made in relation to an entity or statement.
- 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_69e245b5e4208190bac8a6509867e394 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa7f583881909e78e8fe2e6e25fe |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:07 p.m.