Triple
T33920991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlito Brigante |
E869605
|
entity |
| Predicate | plansToMoveTo |
P153881
|
FINISHED |
| Object | Bahamas |
—
|
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: Bahamas | Statement: [Carlito Brigante, plansToMoveTo, Bahamas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plansToMoveTo Context triple: [Carlito Brigante, plansToMoveTo, Bahamas]
-
A.
movedOn
Indicates that an entity changed its position or location from one place to another at some point in time.
-
B.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
-
C.
hasRelocationPlan
chosen
Indicates that an entity has an established or intended plan to move from its current location to a different one.
-
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.
movedIn
Indicates that an entity has taken up residence or established occupancy at a new location or dwelling.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:49 a.m.