Triple
T32464825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emmet Spiceland |
E829671
|
entity |
| Predicate | locationOfFirstSuccess |
P133930
|
FINISHED |
| Object | Ireland |
E5475
|
NE 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: Ireland | Statement: [Emmet Spiceland, locationOfFirstSuccess, Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfFirstSuccess Context triple: [Emmet Spiceland, locationOfFirstSuccess, Ireland]
-
A.
firstSuccessfulRealizationLocation
chosen
Indicates the location where something was first successfully realized, implemented, or achieved.
-
B.
firstLocation
Indicates the initial or primary place where an entity is situated, originates, or where an event or relationship begins.
-
C.
successorLocation
Indicates that one location directly follows or comes after another in a defined spatial or ordered sequence.
-
D.
firstSeriesLocation
Indicates the location where a series first took place, was set, or was initially released.
-
E.
firstAppearsAtLocation
Indicates the initial location where an entity is first observed, introduced, or comes into existence within a given context or sequence.
- F. None of above.
Provenance (4 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0301289dbc8190a4372958d3451171 |
completed | May 12, 2026, 10:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a346663b43881909e501b76f37c7c13 |
completed | June 18, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_6a0300d4185c8190a383d5da3659bc4f |
completed | May 12, 2026, 10:28 a.m. |
Created at: May 1, 2026, 12:57 a.m.