Triple
T25619478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California landscapes |
E642252
|
entity |
| Predicate | includeFeature |
P101663
|
FINISHED |
| Object | Pacific coastline |
—
|
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: Pacific coastline | Statement: [California landscapes, includeFeature, Pacific coastline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeFeature Context triple: [California landscapes, includeFeature, Pacific coastline]
-
A.
includesFeatureTypes
chosen
Indicates that an entity contains or encompasses specific types of features as part of its composition or definition.
-
B.
mayIncludeFeature
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
-
C.
isFeatureOf
Indicates that something functions as a characteristic, attribute, or component belonging to or describing another entity.
-
D.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 21, 2026, 5:02 p.m.