Triple
T18687448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monterey pine |
E456904
|
entity |
| Predicate | nativeRangeType |
P132284
|
FINISHED |
| Object | coastal |
—
|
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: coastal | Statement: [Monterey pine, nativeRangeType, coastal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeRangeType Context triple: [Monterey pine, nativeRangeType, coastal]
-
A.
nativeRange
Indicates the geographic area where an entity naturally occurs or originated without human introduction.
-
B.
nativeRangeIncludes
Indicates that the natural, original geographic distribution of one entity (typically a species) encompasses or occurs within the area defined by another entity.
-
C.
rangeType
Indicates the type or category of values that can appear in the range (output) position of a property or relation.
-
D.
isoRangeNative
Indicates that two values fall within the same native ISO-defined range or interval, according to the system’s inherent ISO-based scale or categorization.
-
E.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2e4c6081908bb958bd00d6bec9 |
completed | April 19, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:49 a.m.