Triple
T37129404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boov |
E919476
|
entity |
| Predicate | relocatesHumansTo |
P1660
|
FINISHED |
| Object | Australia (in the film Home) |
—
|
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: Australia (in the film Home) | Statement: [Boov, relocatesHumansTo, Australia (in the film Home)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocatesHumansTo Context triple: [Boov, relocatesHumansTo, Australia (in the film Home)]
-
A.
relocatedWithin
Indicates that an entity has moved from one location to another while remaining within the same broader area or jurisdiction.
-
B.
relocated
Indicates that an entity has moved or been moved from one location or position to another.
-
C.
relocatedUnder
Indicates that one entity has been moved to a new position or jurisdiction that is subordinate to or contained within another entity.
-
D.
mayRelocateTo
Indicates that an entity has the possibility or permission to move or be moved from its current location to another specified location.
-
E.
relocatedTo
chosen
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.