Triple
T20704298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartina alterniflora |
E508859
|
entity |
| Predicate | foundInZone |
P9687
|
FINISHED |
| Object | low marsh zone |
—
|
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: low marsh zone | Statement: [Spartina alterniflora, foundInZone, low marsh zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInZone Context triple: [Spartina alterniflora, foundInZone, low marsh zone]
-
A.
foundInDepthZone
Indicates that one entity is located within or occurs in a specified depth zone.
-
B.
foundInRegion
chosen
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
C.
foundInRite
Indicates that something (such as an element, object, or action) occurs within, is used in, or is otherwise present as part of a specific rite or ritual.
-
D.
foundInVolume
Indicates that one entity is physically or logically contained within, or occurs in, a specific volume (such as a book volume, data volume, or bounded collection).
-
E.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c18ea874819092a125d9f929a311 |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:13 p.m.