Triple
T35262821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expressways to Prosperity |
E1018413
|
entity |
| Predicate | typeOfMessage |
P4224
|
FINISHED |
| Object | development-oriented motto |
—
|
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-oriented motto | Statement: [Expressways to Prosperity, typeOfMessage, development-oriented motto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMessage Context triple: [Expressways to Prosperity, typeOfMessage, development-oriented motto]
-
A.
typeOfBody
Indicates that one entity is the classification or kind of physical body that the other entity is.
-
B.
relatedMessageType
Indicates that one message is associated with another by specifying the type or category of that related message.
-
C.
definesMessageType
Indicates that one entity specifies or determines the message type classification or category for another entity.
-
D.
typeOf
chosen
Indicates that one entity is a specific kind, class, or category instance of another more general entity.
-
E.
precedesMessageType
Indicates that one message type must occur or be processed before another specified message type.
- 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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a01a0b63d148190b10206509c0a0a5b |
completed | May 11, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_6a01a0245d4c8190a3c3fbbe83f0389d |
completed | May 11, 2026, 9:23 a.m. |
Created at: May 3, 2026, 4:02 p.m.