Triple
T30098241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 19th-century Connecticut |
E764923
|
entity |
| Predicate | joinedUnionAsStateNumber |
P28957
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [19th-century Connecticut, joinedUnionAsStateNumber, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedUnionAsStateNumber Context triple: [19th-century Connecticut, joinedUnionAsStateNumber, 5]
-
A.
admittedToUnionAsStateNumber
chosen
Indicates the ordinal position at which an entity (typically a U.S. state) was formally admitted into a political union as a state.
-
B.
joinedUnitedStatesAsState
Indicates that an entity became a member state of the United States, formally joining the Union.
-
C.
joinedIndependentState
Indicates that an entity became a member of an independent state, typically by formally joining or being incorporated into that sovereign political unit.
-
D.
enteredUnionWithState
Indicates that an entity became a member of, or was formally admitted into, a particular state or political union.
-
E.
participatingState
Indicates that a state is taking part in, or is formally involved as a participant in, a specified event, process, or arrangement.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d92dbdc8190ae3e8f67b979cb5c |
completed | May 2, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:07 p.m.