Triple
T30967485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codling Wind Park |
E788997
|
entity |
| Predicate | plannedNear |
P35436
|
FINISHED |
| Object | east coast of Ireland |
—
|
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: east coast of Ireland | Statement: [Codling Wind Park, plannedNear, east coast of Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedNear Context triple: [Codling Wind Park, plannedNear, east coast of Ireland]
-
A.
plannedLocation
chosen
Indicates the intended or scheduled location where an entity is expected to be or an event is planned to occur.
-
B.
meetsNear
Indicates that two entities meet or come together at a location that is in close proximity to a specified reference point or area.
-
C.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
D.
nearbyEvent
Indicates that one event occurs close in space or time to another event.
-
E.
plannedVia
Indicates that something is arranged, organized, or scheduled by means of a particular method, process, or intermediary.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 8:54 p.m.