Triple
T26145630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindustan Motors |
E659653
|
entity |
| Predicate | ambassadorOriginModel |
P161681
|
FINISHED |
| Object | Morris Oxford Series III |
—
|
NE NERFINISHED |
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: Morris Oxford Series III | Statement: [Hindustan Motors, ambassadorOriginModel, Morris Oxford Series III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ambassadorOriginModel Context triple: [Hindustan Motors, ambassadorOriginModel, Morris Oxford Series III]
-
A.
ambassadorLayout
Indicates a spatial or structural arrangement specifically associated with an ambassador’s position, role, or environment.
-
B.
hasAmbassador
Indicates that one entity serves as an official diplomatic representative (ambassador) for another entity.
-
C.
currentAmbassador
Indicates that one entity currently serves as the official ambassador representing another entity.
-
D.
servedAsAmbassadorInCity
Indicates that an entity held the official position of ambassador while stationed in a specified city.
-
E.
missionOrigin
Indicates the place, organization, or context from which a mission is initiated or originates.
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f6200ac60481909895c61d050b1338 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 26, 2026, 8:22 p.m.