Triple
T6053832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montgomery Canal |
E134857
|
entity |
| Predicate | notableForSpecies |
P965
|
FINISHED |
| Object | aquatic plants |
—
|
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: aquatic plants | Statement: [Montgomery Canal, notableForSpecies, aquatic plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableForSpecies Context triple: [Montgomery Canal, notableForSpecies, aquatic plants]
-
A.
notableSpecies
chosen
Indicates that the subject is known for, or significantly associated with, the specified species.
-
B.
notableSpeciesRole
Indicates that a species plays a particularly important, characteristic, or influential role in relation to another entity or context.
-
C.
notableSpeciesGroup
Indicates that an entity is a significant or characteristic member of a particular species group associated with another entity.
-
D.
commonNameOfNotableSpecies
Indicates that the subject is a commonly used vernacular or everyday name for a notable or well-known biological species.
-
E.
hasNotableSpecimen
Indicates that an entity possesses or is associated with a specimen that is considered particularly significant, remarkable, or noteworthy.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05708fda48190ad3d1860969ebb6a |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:09 p.m.