Triple
T4688195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Non-Annex I Parties |
E103970
|
entity |
| Predicate | typicalEconomicStatus |
P2987
|
FINISHED |
| Object | developing countries |
—
|
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: developing countries | Statement: [Non-Annex I Parties, typicalEconomicStatus, developing countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEconomicStatus Context triple: [Non-Annex I Parties, typicalEconomicStatus, developing countries]
-
A.
middleClass
Indicates that an entity belongs to the socioeconomic group characterized as the middle class.
-
B.
economicStatus
chosen
Indicates the financial or socioeconomic condition or standing of an entity relative to others or to defined economic criteria.
-
C.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
D.
traditionalSocialClass
Indicates that an entity belongs to or is associated with a particular traditional social class within a social hierarchy.
-
E.
typicalHouse
Indicates that something is a standard or representative example of a house in terms of its usual features, structure, or characteristics.
- 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd66059bfc8190885d26d05dd38df1 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd6219da948190bbbb50f08573ab4d |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.