Triple
T34251386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamatai (fictional island) |
E878752
|
entity |
| Predicate | primaryProtagonistOnIsland |
P32529
|
FINISHED |
| Object | Lara Croft |
E193996
|
NE 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: Lara Croft | Statement: [Yamatai (fictional island), primaryProtagonistOnIsland, Lara Croft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryProtagonistOnIsland Context triple: [Yamatai (fictional island), primaryProtagonistOnIsland, Lara Croft]
-
A.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
B.
protagonistIs
chosen
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
C.
onProtectedIsland
Indicates that one entity is located on an island that has protected or restricted status.
-
D.
isPrincipalInhabitedIslandOf
Indicates that one island serves as the main or most significant inhabited island within the territory, region, or group associated with another entity.
-
E.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
- F. None of above.
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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37c61418108190b057bdb271aa1bdb |
completed | June 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:56 a.m.