Triple
T27371967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tontemboan people |
E690347
|
entity |
| Predicate | urbanMigrationDestination |
P43380
|
FINISHED |
| Object | Manado |
—
|
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: Manado | Statement: [Tontemboan people, urbanMigrationDestination, Manado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanMigrationDestination Context triple: [Tontemboan people, urbanMigrationDestination, Manado]
-
A.
cityAfterRelocation
Indicates the city where an entity is located after it has been moved or relocated from a previous place.
-
B.
hasSignificantEmigrationTo
chosen
Indicates that a substantial number of people leave one place, group, or entity to move and settle in another specific place, group, or entity.
-
C.
typicalDestinationMetroArea
Indicates the metro area that is most commonly the destination associated with a given origin or context.
-
D.
nearestLargeUrbanArea
Indicates that one entity is the closest major city or large urban center to the other entity.
-
E.
immigratedTo
Indicates that an entity moved from its country of origin to live permanently in another specified country or region.
- 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 12:19 p.m.