Triple
T27941651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grace Augustine |
E700763
|
entity |
| Predicate | attemptedTransferTo |
P57570
|
FINISHED |
| Object | Na'vi avatar body |
—
|
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: Na'vi avatar body | Statement: [Grace Augustine, attemptedTransferTo, Na'vi avatar body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptedTransferTo Context triple: [Grace Augustine, attemptedTransferTo, Na'vi avatar body]
-
A.
allowsTransferTo
Indicates that one entity permits or enables the transfer of something (such as rights, funds, or data) to another specified entity.
-
B.
transferAfter
Indicates that one entity transfers something to another entity only after a specified event or condition has occurred.
-
C.
transferredWith
Indicates that something was moved or conveyed from one entity to another using a specified medium, method, or accompanying item.
-
D.
hasTransfer
Indicates a relationship where something is moved or conveyed from one entity or location to another.
-
E.
transferDestination
chosen
Indicates the entity that serves as the receiving end or target location of a transfer from 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:18 p.m.