Triple
T34121762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosha |
E875157
|
entity |
| Predicate | hasMigrationOrigin |
P7845
|
FINISHED |
| Object | northwestern India |
—
|
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: northwestern India | Statement: [Bosha, hasMigrationOrigin, northwestern India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMigrationOrigin Context triple: [Bosha, hasMigrationOrigin, northwestern India]
-
A.
hasMigrationHistoryFrom
chosen
Indicates that an entity has a recorded history of migrating or moving from a specified origin location or source.
-
B.
hasMigrationTo
Indicates a directed movement or transfer from one place, system, or state to another.
-
C.
hasReasonForMigration
Indicates that there exists a specific cause, motive, or justification for an entity’s act of migrating from one place to another.
-
D.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
E.
hasOriginFeature
Indicates that an entity possesses a specific characteristic, attribute, or feature related to its origin or source.
- 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 1, 2026, 1:53 a.m.