Triple
T4434225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L-Town |
E95607
|
entity |
| Predicate | hasCapitalRoleViaReferent |
P18085
|
FINISHED |
| Object | state capital of Michigan |
—
|
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: state capital of Michigan | Statement: [L-Town, hasCapitalRoleViaReferent, state capital of Michigan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalRoleViaReferent Context triple: [L-Town, hasCapitalRoleViaReferent, state capital of Michigan]
-
A.
hasCapitalRole
chosen
Indicates that an entity holds an official role, function, or status specifically associated with a capital city.
-
B.
hasCapitalOwnerRole
Indicates that an entity holds the role or status of owning capital in relation to another entity or asset.
-
C.
refersToRole
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
-
D.
hasCapital
Indicates that a place or political entity has a specific city designated as its capital.
-
E.
hasCapitalDescribed
Indicates that an entity’s capital city is being described or specified in relation to that entity.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35588e99881908fea7b71a33e2bb6 |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:31 p.m.