Triple
T37593982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raseiniai uezd |
E935329
|
entity |
| Predicate | includedLocalities |
P129318
|
FINISHED |
| Object | town of Raseiniai |
E1259422
|
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: town of Raseiniai | Statement: [Raseiniai uezd, includedLocalities, town of Raseiniai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedLocalities Context triple: [Raseiniai uezd, includedLocalities, town of Raseiniai]
-
A.
hasLocalities
chosen
Indicates that an entity is associated with, contains, or is linked to one or more specific geographic or administrative local areas.
-
B.
hasUrbanLocalities
Indicates that an entity possesses or includes one or more urban localities within its jurisdiction or scope.
-
C.
hasTypeOfLocalities
Indicates that an entity is associated with, or classified by, specific types or categories of localities (e.g., urban, rural, suburban).
-
D.
hasMultipleLocalities
Indicates that an entity is associated with more than one locality or geographic area.
-
E.
townIncluded
Indicates that one town is geographically or administratively contained within another specified area or jurisdiction.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40a800a918819081ad0e2943ad0cfd |
completed | June 28, 2026, 4:50 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.