Triple
T18987986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surf City, New Jersey |
E464604
|
entity |
| Predicate | partOfIslandChain |
P67106
|
FINISHED |
| Object | barrier islands of the New Jersey coast |
—
|
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: barrier islands of the New Jersey coast | Statement: [Surf City, New Jersey, partOfIslandChain, barrier islands of the New Jersey coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfIslandChain Context triple: [Surf City, New Jersey, partOfIslandChain, barrier islands of the New Jersey coast]
-
A.
locatedInArchipelago
Indicates that one place or geographic entity is situated within or is part of a specific archipelago.
-
B.
islandChain
chosen
Indicates that one landmass is part of a series of islands that are geographically connected or aligned with each other.
-
C.
partOfIsland
Indicates that one entity is a portion or component of an island.
-
D.
islandOf
Indicates that one place is an island belonging to, located within, or geographically associated with another specified area or body of land/water.
-
E.
associatedIsland
Indicates that one entity is related to or connected with a particular island in some relevant way.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6618ab881909c0ed94930e42e68 |
completed | April 20, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.