Triple
T4019659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town Hall of Kaunas |
E91248
|
entity |
| Predicate | hasFunctionInPast |
P20953
|
FINISHED |
| Object | city council seat |
—
|
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: city council seat | Statement: [Town Hall of Kaunas, hasFunctionInPast, city council seat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunctionInPast Context triple: [Town Hall of Kaunas, hasFunctionInPast, city council seat]
-
A.
hadFunction
chosen
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
B.
hasFormerUse
Indicates that something previously served a particular function or role that it no longer has.
-
C.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
D.
hasHistorySince
Indicates that an entity has maintained a particular state, condition, or relationship continuously starting from a specified point in time.
-
E.
hasFunctionInComplex
Indicates that an entity performs a specific functional role within a larger molecular or structural complex.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaab39d4819080e37cd175c89542 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.