Triple
T643828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. Butler |
E11198
|
entity |
| Predicate | subsequentDevelopment |
P13185
|
FINISHED |
| Object | later limited by Helvering v. Davis |
—
|
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: later limited by Helvering v. Davis | Statement: [United States v. Butler, subsequentDevelopment, later limited by Helvering v. Davis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentDevelopment Context triple: [United States v. Butler, subsequentDevelopment, later limited by Helvering v. Davis]
-
A.
laterDevelopments
chosen
Indicates that subsequent events, changes, or outcomes occurred following an earlier situation or state.
-
B.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
C.
development
Indicates a process or relationship in which something grows, advances, or becomes more complex or mature over time.
-
D.
developedAlong
Indicates that something was created, constructed, or evolved following the course, path, or boundary of something else.
-
E.
developed
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f18216081908331aa12dac40214 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0a0ab481909871461418a00be7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.