Triple
T21080290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoreline |
E519345
|
entity |
| Predicate | hasAuthorialStyleFeature |
P27486
|
FINISHED |
| Object | engagement with place |
—
|
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: engagement with place | Statement: [Shoreline, hasAuthorialStyleFeature, engagement with place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorialStyleFeature Context triple: [Shoreline, hasAuthorialStyleFeature, engagement with place]
-
A.
hasAuthorCharacteristic
Indicates that an author possesses a particular attribute, trait, or quality.
-
B.
hasEditorialStyle
Indicates that one entity possesses, applies, or is characterized by a particular editorial style defined by another entity.
-
C.
authorStyle
chosen
Indicates the stylistic characteristics or manner of expression associated with a particular author in their works.
-
D.
hasAuthorialStance
Indicates that an entity expresses, embodies, or is associated with a particular author’s viewpoint, attitude, or perspective toward its subject matter.
-
E.
hasLyricalStyle
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity or context.
- 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702da7be881908e430518103d7bb1 |
completed | April 21, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:49 p.m.