Triple
T29302575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fadicca |
E742999
|
entity |
| Predicate | traditionallyLivesAlong |
P112276
|
FINISHED |
| Object | Nile River |
—
|
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: Nile River | Statement: [Fadicca, traditionallyLivesAlong, Nile River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyLivesAlong Context triple: [Fadicca, traditionallyLivesAlong, Nile River]
-
A.
traditionallyLivedTo
Indicates that an entity customarily or historically resided in a particular place or environment over an extended period.
-
B.
traditionallyResidesIn
chosen
Indicates that an entity customarily lives or has its long-established home in a particular place or region.
-
C.
traditionalLifestyleRegion
Indicates that a region is characterized by or associated with a traditional lifestyle or way of living.
-
D.
traditionalLifestyle
Indicates that an entity follows or maintains long-established customs, practices, and ways of living, typically in contrast to modern or industrialized lifestyles.
-
E.
traditionalLifestyleStatus
Indicates the extent to which an entity follows, maintains, or is characterized by a traditional way of life or customary practices.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 28, 2026, 1:10 p.m.