Triple
T34843025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatar Peninsula |
E1004391
|
entity |
| Predicate | hasCapitalOn |
P204
|
FINISHED |
| Object | Doha |
—
|
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: Doha | Statement: [Qatar Peninsula, hasCapitalOn, Doha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalOn Context triple: [Qatar Peninsula, hasCapitalOn, Doha]
-
A.
hasCapital
chosen
Indicates that a place or political entity has a specific city designated as its capital.
-
B.
hasCapitalSee
Indicates that one entity (typically a country, state, or organization) possesses a designated capital city or principal seat of authority in the other entity.
-
C.
hasCapitalFeature
Indicates that one entity possesses or is characterized by a primary or most important feature represented by the other entity.
-
D.
hasCapitalUT
Indicates that a political or administrative entity has a specific city as its capital, with the relation defined using untyped (UT) resources.
-
E.
hasLaterCapital
Indicates that one entity’s designation or establishment as a capital city occurred later in time than that of another 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7c96e6dc8190b89554480ebcea39 |
completed | May 9, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69ff7c2381748190ad9a2176e0e478cd |
completed | May 9, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4 p.m.