Triple
T3681756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poznań Town Hall |
E78127
|
entity |
| Predicate | mechanicalGoatsDisplayTime |
P50283
|
FINISHED |
| Object | 12:00 |
—
|
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: 12:00 | Statement: [Poznań Town Hall, mechanicalGoatsDisplayTime, 12:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanicalGoatsDisplayTime Context triple: [Poznań Town Hall, mechanicalGoatsDisplayTime, 12:00]
-
A.
clockType
Indicates the type or category of a clock associated with an entity (e.g., analog, digital, system clock, etc.).
-
B.
hasClockFaces
Indicates that an object is equipped with one or more clock faces.
-
C.
clockMechanismCompletedInYear
Indicates that the construction or completion of a clock mechanism occurred in a specified year.
-
D.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
-
E.
clockMechanismDesigner
Indicates that one entity is the designer or creator of the mechanism of a clock associated with another entity.
- 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_69ad85e18c1c8190be8aafb227f39f48 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc492aed481909e8986378ad283fc |
completed | March 8, 2026, 6:48 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb97cdb788190a5ce96b21bd157ab |
completed | March 8, 2026, 6:01 p.m. |
Created at: March 8, 2026, 3:25 p.m.