Triple
T19460550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorial Middle School |
E486855
|
entity |
| Predicate | locatedInCoastalTown |
P104129
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Memorial Middle School, locatedInCoastalTown, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCoastalTown Context triple: [Memorial Middle School, locatedInCoastalTown, true]
-
A.
isInCoastalTown
chosen
Indicates that one entity (typically a place or object) is located within a town that is situated along a coast.
-
B.
locatedInWaterfrontTown
Indicates that the subject is situated within a town that is directly adjacent to or closely associated with a body of water, such as a sea, lake, or river.
-
C.
includesCoastalTown
Indicates that a geographic area or region contains at least one town located on or directly adjacent to a coastline.
-
D.
locatedOnCoastAt
Indicates that one entity is situated on the coastline at the specific location represented by another entity.
-
E.
isCoastalLocality
Indicates that a locality is situated on or directly adjacent to a sea, ocean, or significant coastal body of water.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633c7f4388190be8c207c94ba8889 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.