Triple
T29548282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polis Massa medical facility |
E749688
|
entity |
| Predicate | sceneLocationFor |
P124600
|
FINISHED |
| Object | Padmé Amidala’s death |
—
|
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: Padmé Amidala’s death | Statement: [Polis Massa medical facility, sceneLocationFor, Padmé Amidala’s death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sceneLocationFor Context triple: [Polis Massa medical facility, sceneLocationFor, Padmé Amidala’s death]
-
A.
hasSceneLocation
chosen
Indicates that a scene or event takes place at, or is set in, a specific location.
-
B.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
C.
captureLocation
Indicates the place where an entity or event is captured, recorded, or taken.
-
D.
plotLocation
Indicates the relationship between a creative work and the place or setting where its story or events occur.
-
E.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66cf471d88190af960f2c9959878e |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 5:09 p.m.