Triple
T4583021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saville Inquiry |
E101897
|
entity |
| Predicate | numberOfWitnessesHeard |
P58125
|
FINISHED |
| Object | over 900 |
—
|
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: over 900 | Statement: [Saville Inquiry, numberOfWitnessesHeard, over 900]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfWitnessesHeard Context triple: [Saville Inquiry, numberOfWitnessesHeard, over 900]
-
A.
witnesses
Indicates that one entity observes an event, action, or situation involving another entity, typically as a bystander or observer.
-
B.
numberOfVictimsClaimedInTestimony
Indicates the quantity of victims that a person asserts or reports in their testimony.
-
C.
hasNumberOfJurors
Indicates the relationship specifying how many jurors are associated with a given legal case, trial, or proceeding.
-
D.
notableWitness
Indicates that one entity is a significant or prominent witness to an event, action, or situation involving another entity.
-
E.
hasTestimony
Indicates that an entity provides, contains, or is associated with a formal statement or account (testimony) about another entity or event.
- F. None of above. chosen
Provenance (4 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59029568819091db1e77a9a2ec41 |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:10 p.m.