Triple
T22960467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Ebble |
E570880
|
entity |
| Predicate | hasRiverBedComposition |
P150394
|
FINISHED |
| Object | chalk |
—
|
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: chalk | Statement: [River Ebble, hasRiverBedComposition, chalk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverBedComposition Context triple: [River Ebble, hasRiverBedComposition, chalk]
-
A.
hasRiverBedType
Indicates the type or classification of the riverbed associated with a given river or watercourse.
-
B.
hasRiverineCharacteristic
Indicates that something possesses qualities, features, or conditions associated with rivers or river environments.
-
C.
hasRiverInfluence
Indicates that one entity affects or is affected by a river in terms of its characteristics, behavior, or conditions.
-
D.
hasRiverBelow
Indicates that one entity is located above another such that a river lies physically below it.
-
E.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
- F. None of above. chosen
Provenance (4 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f3c96081909abd6ec32103d4c3 |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:47 p.m.