Triple
T544100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doha |
E12693
|
entity |
| Predicate | developmentCharacteristic |
P662
|
FINISHED |
| Object | rapidly developing city |
—
|
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: rapidly developing city | Statement: [Doha, developmentCharacteristic, rapidly developing city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentCharacteristic Context triple: [Doha, developmentCharacteristic, rapidly developing city]
-
A.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
B.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
C.
keyFeature
Indicates that something is a primary, distinguishing, or most important feature of an entity.
-
D.
demographicsCharacteristic
Indicates that one entity serves as a demographic attribute or characteristic (such as age, gender, ethnicity, etc.) that describes or classifies another entity.
-
E.
development
Indicates a process or relationship in which something grows, advances, or becomes more complex or mature over time.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a498dea88881908a938fe8f2313bec |
completed | March 1, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69a494b8098481908097228db8ad0262 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.