Triple
T9968691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amnesty Bay |
E195747
|
entity |
| Predicate | inspiredByRealWorldRegion |
P17515
|
FINISHED |
| Object | coast of Maine |
—
|
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: coast of Maine | Statement: [Amnesty Bay, inspiredByRealWorldRegion, coast of Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredByRealWorldRegion Context triple: [Amnesty Bay, inspiredByRealWorldRegion, coast of Maine]
-
A.
inspiredByPlace
Indicates that something (such as a work, idea, or creation) originates from or is significantly influenced by a particular location or environment.
-
B.
mentionsRegion
Indicates that one entity explicitly refers to or cites a specific geographic region in its content or context.
-
C.
placeRegion
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
D.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
E.
basedOnRealRegion
chosen
Indicates that something is derived from, inspired by, or corresponds to an actual geographic or administrative region in the real world.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb7b683ac8190ac97bd775a860d29 |
completed | April 2, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:47 p.m.