Triple
T31120011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland congressional delegation |
E793196
|
entity |
| Predicate | stateCapitalRepresented |
P71239
|
FINISHED |
| Object | Annapolis |
—
|
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: Annapolis | Statement: [Maryland congressional delegation, stateCapitalRepresented, Annapolis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateCapitalRepresented Context triple: [Maryland congressional delegation, stateCapitalRepresented, Annapolis]
-
A.
governingStateCapital
Indicates that a state serves as the governing political authority over the specified capital city.
-
B.
capitalCityOfAssociatedState
chosen
Indicates that a city serves as the capital of the state with which another entity is associated.
-
C.
isStateCapital
Indicates that a city serves as the official capital of a given state.
-
D.
capitalOfMajorState
Indicates that one location serves as the primary capital city of a major state or significant administrative region.
-
E.
stateCapitalConnection
Indicates a relationship where one entity is the capital city of a given state or is otherwise connected to that state in its role as capital.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 29, 2026, 9:04 p.m.