Triple
T38615150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethiope River |
E934593
|
entity |
| Predicate | sourceDescription |
P163471
|
FINISHED |
| Object | emerges from the roots of a giant tree |
—
|
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: emerges from the roots of a giant tree | Statement: [Ethiope River, sourceDescription, emerges from the roots of a giant tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceDescription Context triple: [Ethiope River, sourceDescription, emerges from the roots of a giant tree]
-
A.
sourceDescribedBy
chosen
Indicates that a source is documented, characterized, or otherwise explained by a particular description or descriptive resource.
-
B.
source
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
C.
sourceStatus
Indicates the current state or condition of a given source within a process, system, or workflow.
-
D.
sourceCategory
Indicates the classification or type from which something originates or is derived.
-
E.
mainSourceType
Indicates the primary category or kind of source from which something originates or is derived.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 3, 2026, 4:32 p.m.