Triple
T35790801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FLIR1 |
E1034685
|
entity |
| Predicate | linkedToWitness |
P56735
|
FINISHED |
| Object | David Fravor |
—
|
NE NERFINISHED |
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: David Fravor | Statement: [FLIR1, linkedToWitness, David Fravor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToWitness Context triple: [FLIR1, linkedToWitness, David Fravor]
-
A.
onlyWitnessOf
Indicates that one entity is the sole witness to an event, action, or situation involving another entity, with no other witnesses present.
-
B.
notableWitness
Indicates that one entity is a significant or prominent witness to an event, action, or situation involving another entity.
-
C.
cooperatingWitness
Indicates that one party is providing assistance or testimony to authorities or another party, typically in an investigative or legal context, in collaboration rather than opposition.
-
D.
witnesses
chosen
Indicates that one entity observes an event, action, or situation involving another entity, typically as a bystander or observer.
-
E.
socialWitness
Indicates that one entity observes, attends, or is present for another entity’s social interaction or socially significant event.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: May 3, 2026, 4:06 p.m.