Triple
T37694014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contract Clause of the U.S. Constitution |
E938878
|
entity |
| Predicate | earlyLeadingCase |
P82359
|
FINISHED |
| Object | Fletcher v. Peck |
—
|
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: Fletcher v. Peck | Statement: [Contract Clause of the U.S. Constitution, earlyLeadingCase, Fletcher v. Peck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyLeadingCase Context triple: [Contract Clause of the U.S. Constitution, earlyLeadingCase, Fletcher v. Peck]
-
A.
leadingCaseOn
chosen
Indicates that one case serves as the primary or authoritative precedent for another case.
-
B.
precededByCapital
Indicates that the referenced element is immediately preceded by a capital letter.
-
C.
earlyLabel
Indicates that one entity assigns or is associated with a label or classification earlier in time than another relevant event or reference point.
-
D.
earlyStrategy
Indicates that an entity adopts or implements a strategy at an early stage or time relative to a process, event, or development.
-
E.
precededAsCapitalBy
Indicates that one capital city previously held the status of capital before being succeeded by another capital city.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.