Triple
T9798944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barker v. Wingo |
E237786
|
entity |
| Predicate | factor |
P90033
|
FINISHED |
| Object | length of delay |
—
|
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: length of delay | Statement: [Barker v. Wingo, factor, length of delay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factor Context triple: [Barker v. Wingo, factor, length of delay]
-
A.
fact
Indicates that something is objectively true or has actually occurred, independent of opinion or belief.
-
B.
faction
Indicates that an entity is formally affiliated with, or belongs to, a particular faction or organized group within a broader context.
-
C.
foundation
Indicates that one entity serves as the base, support, or underlying basis upon which another entity is built, established, or depends.
-
D.
fine
Indicates that an authority imposes a monetary penalty on an entity for violating a rule, law, or agreement.
-
E.
fault
Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda627cc2c81909ccc2e26751f5e85 |
completed | April 1, 2026, 11:11 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:28 p.m.