Triple
T25080469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IJ basin |
E628171
|
entity |
| Predicate | hasMorphologyCharacterizedBy |
P112583
|
FINISHED |
| Object | former tidal channels |
—
|
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: former tidal channels | Statement: [IJ basin, hasMorphologyCharacterizedBy, former tidal channels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMorphologyCharacterizedBy Context triple: [IJ basin, hasMorphologyCharacterizedBy, former tidal channels]
-
A.
hasMorphologyDistinctFrom
Indicates that the morphology (form or structure) of one entity is different from that of another entity.
-
B.
hasUnusualMorphology
Indicates that an entity possesses structural or anatomical features that deviate significantly from what is typical or expected for its kind.
-
C.
hasMorphologicalState
chosen
Indicates that an entity possesses or is characterized by a particular morphological condition, form, or structural state.
-
D.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
E.
hasMorphologicalType
Indicates that an entity possesses or is classified by a particular morphological type or structural form.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 18, 2026, 6:22 a.m.