Triple
T1173530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Asian Tigers |
E24965
|
entity |
| Predicate | usedAsCaseStudyIn |
P2398
|
FINISHED |
| Object | development economics |
—
|
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: development economics | Statement: [Four Asian Tigers, usedAsCaseStudyIn, development economics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCaseStudyIn Context triple: [Four Asian Tigers, usedAsCaseStudyIn, development economics]
-
A.
hasCaseStudy
chosen
Indicates that one entity is documented, illustrated, or analyzed by a specific case study associated with it.
-
B.
usedInCase
Indicates that something (such as an item, method, or piece of information) is employed or applied within a particular case or instance.
-
C.
developedInCase
Indicates that something (such as a method, argument, or principle) was formulated, articulated, or established within the context of a particular case.
-
D.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
E.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd53e4b48190abb2167f8074a6bc |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5844348190b01ac6506906ba3b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.