Triple
T24915274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kissing Point |
E623965
|
entity |
| Predicate | hasCurrentNameUsage |
P130354
|
FINISHED |
| Object | Kissing Point Park |
—
|
NE NERFINISHED |
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: Kissing Point Park | Statement: [Kissing Point, hasCurrentNameUsage, Kissing Point Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentNameUsage Context triple: [Kissing Point, hasCurrentNameUsage, Kissing Point Park]
-
A.
hasGivenNameUsage
Indicates that an entity is associated with a particular way or context in which its given name is used.
-
B.
hasCurrentNameContext
chosen
Indicates that an entity is associated with the name it currently uses or is recognized by in the present context.
-
C.
currentNameUsedFrom
Indicates that an entity’s currently used name has been in effect starting from a specified point in time or source.
-
D.
nameUsedBy
Indicates that a particular name is employed or referenced by a specific entity.
-
E.
hasFullNameUsage
Indicates that an entity uses a particular full name in a specific context or manner.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 18, 2026, 5:28 a.m.