Triple
T38075209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lielupe River island |
E950693
|
entity |
| Predicate | hasLocatedOnIt |
P200955
|
FINISHED |
| Object | Jelgava Palace |
—
|
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: Jelgava Palace | Statement: [Lielupe River island, hasLocatedOnIt, Jelgava Palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocatedOnIt Context triple: [Lielupe River island, hasLocatedOnIt, Jelgava Palace]
-
A.
hadLocation
Indicates that an entity was situated at, or associated with, a specific location during a particular time or context.
-
B.
hasGround
Indicates that one entity possesses, is supported by, or is associated with a ground or base surface.
-
C.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
D.
hasPositionOn
Indicates that one entity occupies or holds a specific role, job, or spatial location relative to another entity.
-
E.
heldAtLocation
Indicates that an entity is being kept or stored at a specific location.
- F. None of above. chosen
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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffbb1c5bf88190a0bf791213045885 |
completed | May 9, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69ffba0ab0f881908f84ef81f7a1bfe8 |
completed | May 9, 2026, 10:49 p.m. |
| PDg | Predicate description generation | batch_69ffbb1b3b888190ba329ad321fc3f3d |
completed | May 9, 2026, 10:54 p.m. |
Created at: May 3, 2026, 4:21 p.m.