Triple
T33020079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mamund |
E844883
|
entity |
| Predicate | crossBorderTribe |
P55550
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mamund, crossBorderTribe, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossBorderTribe Context triple: [Mamund, crossBorderTribe, true]
-
A.
crossBorderCommunity
chosen
Indicates a relationship where a community spans or connects populations across one or more political or geographic borders.
-
B.
crossBorderRegion
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
C.
crossBorderAgglomerationWith
Indicates a relationship where economic or spatial clustering of activities spans or connects across a national or regional border between the linked entities.
-
D.
crossBorderPeople
Indicates the movement or presence of people across national or regional borders.
-
E.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
- 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 1, 2026, 1:23 a.m.