Triple
T37489617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jita people |
E931638
|
entity |
| Predicate | resideAround |
P41003
|
FINISHED |
| Object | southern shores of Lake Victoria |
—
|
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: southern shores of Lake Victoria | Statement: [Jita people, resideAround, southern shores of Lake Victoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resideAround Context triple: [Jita people, resideAround, southern shores of Lake Victoria]
-
A.
residesNear
chosen
Indicates that one entity lives or is located in close physical proximity to another entity.
-
B.
residesUnder
Indicates that one entity lives or is situated beneath another entity in a hierarchical or spatial structure.
-
C.
isOftenLocatedAround
Indicates that one entity is frequently found in the vicinity of, or surrounding, another entity.
-
D.
residesOver
Indicates that one entity lives or is situated in a position physically higher than or above another entity.
-
E.
centeredAtResidence
Indicates that an entity’s primary focus, activity, or presence is located at a specified residence.
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.