Triple
T20634225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Datsun |
E507035
|
entity |
| Predicate | revivalStrategy |
P140848
|
FINISHED |
| Object | emerging markets focus |
—
|
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: emerging markets focus | Statement: [Datsun, revivalStrategy, emerging markets focus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalStrategy Context triple: [Datsun, revivalStrategy, emerging markets focus]
-
A.
restartPolicy
Indicates the rules governing if and how an action, process, or task should automatically restart after it stops or fails.
-
B.
revivalCenter
Indicates that an entity serves as a central place or hub where revival, restoration, or renewal activities for another entity occur.
-
C.
revival
Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
-
D.
revivalEndTime
Indicates the point in time at which a revival process, event, or restored state comes to an end.
-
E.
revivedAfter
Indicates that one entity comes back to life or is restored to a living or active state after a period of being dead, inactive, or nonfunctional, following another event or time point.
- F. None of above. chosen
Provenance (4 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad0d808c81908a60abd02a22ed92 |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:42 a.m.