Triple
T18815493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubrovnik Bell Tower |
E460123
|
entity |
| Predicate | mechanicalFiguresType |
P58268
|
FINISHED |
| Object | bronze bell-strikers |
—
|
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: bronze bell-strikers | Statement: [Dubrovnik Bell Tower, mechanicalFiguresType, bronze bell-strikers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanicalFiguresType Context triple: [Dubrovnik Bell Tower, mechanicalFiguresType, bronze bell-strikers]
-
A.
typeOfFigure
Indicates that one entity is a specific kind or category of geometric figure relative to another.
-
B.
hasAnimatedFigures
chosen
Indicates that something contains or features figures that are animated or capable of motion.
-
C.
numberOfFiguresDepicted
Indicates the total count of distinct figures shown within a given depiction or representation.
-
D.
isToyToLifeFigure
Indicates that an object is a physical toy figure designed to be digitally activated or used within a video game or virtual environment.
-
E.
mechanicalFunction
Indicates that one entity serves as the mechanical role, operation, or function performed by another entity or system.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3e092e081908fc310c70f646e79 |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.