Triple
T10964440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State of New Columbia |
E259058
|
entity |
| Predicate | wouldHave |
P13998
|
FINISHED |
| Object | two U.S. senators (proposed) |
—
|
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: two U.S. senators (proposed) | Statement: [State of New Columbia, wouldHave, two U.S. senators (proposed)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wouldHave Context triple: [State of New Columbia, wouldHave, two U.S. senators (proposed)]
-
A.
wouldHaveHadMembers
chosen
Indicates a hypothetical or counterfactual relationship in which an entity, under certain conditions or in an unrealized scenario, would have included specific members.
-
B.
wouldHaveHeldPosition
Indicates that an entity was expected or intended to occupy a particular role or office, but did not actually hold it in reality.
-
C.
have
Indicates that one entity possesses, owns, or contains another entity or attribute.
-
D.
wouldProvide
Indicates that one entity is willing or expected to supply or furnish something to another entity under certain conditions.
-
E.
couldConsider
Indicates that one entity has the potential or option to take another entity into account when making a decision, judgment, or evaluation.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77148c4588190ad0f2b54ee4bab98 |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e8c27cc81908050590b7a04cafd |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.