Triple
T27940757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | oceans of Pandora |
E700732
|
entity |
| Predicate | exploredByCharacter |
P62826
|
FINISHED |
| Object | Jake Sully |
—
|
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: Jake Sully | Statement: [oceans of Pandora, exploredByCharacter, Jake Sully]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploredByCharacter Context triple: [oceans of Pandora, exploredByCharacter, Jake Sully]
-
A.
visitedByCharacter
chosen
Indicates that a location or place is visited or physically gone to by a specific character.
-
B.
exploitedByCharacter
Indicates that a character takes unfair advantage of, manipulates, or otherwise uses another entity for their own benefit.
-
C.
explorationBy
Indicates a relationship where one entity conducts or performs exploration directed at or involving another entity.
-
D.
experiencedByCharacter
Indicates that a particular event, situation, or emotion is undergone or lived through by a specific character.
-
E.
willBeExploredBy
Indicates that something is expected or planned to be examined, investigated, or studied by a particular agent in the future.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 7:17 p.m.