Triple
T31446145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Naveen |
E802190
|
entity |
| Predicate | laterWeddingLocation |
P27490
|
FINISHED |
| Object | Tiana's Palace |
—
|
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: Tiana's Palace | Statement: [Prince Naveen, laterWeddingLocation, Tiana's Palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterWeddingLocation Context triple: [Prince Naveen, laterWeddingLocation, Tiana's Palace]
-
A.
locationOfLaterMeeting
Indicates the place where a subsequent or future meeting is scheduled or expected to occur.
-
B.
laterLocation
Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
-
C.
marriageLocation
chosen
Indicates the place where a marriage ceremony or legal union between two people took place.
-
D.
laterReception
Indicates that one entity receives or accepts something at a time that is later than when another related reception or event occurs.
-
E.
secondEventLocation
Indicates the location where the second event in a sequence takes place.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
Created at: April 30, 2026, 9:09 p.m.