Triple
T9130635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor Tree |
E219075
|
entity |
| Predicate | returnedIn |
P82662
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Survivor Tree, returnedIn, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedIn Context triple: [Survivor Tree, returnedIn, 2010]
-
A.
wasReturnedIn
Indicates that an item previously taken or sent was brought or sent back to its original source or owner at a specific time or in a specific context.
-
B.
returnedBy
Indicates that something is given, sent, or brought back to a previous sender, owner, or source by another entity.
-
C.
returnedDuring
chosen
Indicates that one entity was given back or restored to another entity within a specified time period or event.
-
D.
wasReturnedTo
Indicates that an entity was sent or brought back to a previous owner, location, or state after having been away or removed.
-
E.
returnedWith
Indicates that an entity came back or was brought back accompanied by, or in possession of, another specified 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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8cdafb48190be5e62b15779d771 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.