Triple
T27707920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICS |
E698601
|
entity |
| Predicate | capitalDefinition |
P172117
|
FINISHED |
| Object | qualifying capital resources |
—
|
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: qualifying capital resources | Statement: [ICS, capitalDefinition, qualifying capital resources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalDefinition Context triple: [ICS, capitalDefinition, qualifying capital resources]
-
A.
capital
Indicates that one place serves as the official seat of government or primary administrative center for another political entity.
-
B.
capitalSince
Indicates that an entity has served as the capital of another entity starting from a specified point in time.
-
C.
capitalContext
Indicates that a location serves as the capital within a specified contextual scope (such as a country, region, or administrative unit).
-
D.
capitalRenamedFrom
Indicates that a capital city previously had a different name, specifying the former name from which it was renamed.
-
E.
capitalPosition
Indicates the spatial or geographic position of a capital relative to some reference location or framework.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 27, 2026, 3 p.m.