Triple
T13840002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maysville Road veto |
E332631
|
entity |
| Predicate | amountOfFederalSubscription |
P111713
|
FINISHED |
| Object | $150,000 |
—
|
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: $150,000 | Statement: [Maysville Road veto, amountOfFederalSubscription, $150,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amountOfFederalSubscription Context triple: [Maysville Road veto, amountOfFederalSubscription, $150,000]
-
A.
federalSubjectCount
Indicates the number of federal subjects (administrative units within a federation) associated with or contained by an entity.
-
B.
numberOfSubscribers
Indicates the total count of subscribers associated with a given entity.
-
C.
federalStatus
Indicates that an entity holds a particular legal or administrative status under federal (national) authority or jurisdiction.
-
D.
canBeFederalizedBy
Indicates that an entity has the legal or practical capacity to be brought under the authority, control, or jurisdiction of a specified federal-level entity.
-
E.
federalSchemeImplemented
Indicates that a specific federal government program or policy has been put into operation or carried out in practice.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02ae5e4c8190ad85ad2968bc71b2 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:13 p.m.