Triple
T28407394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torre Monumental |
E719568
|
entity |
| Predicate | hasClockMechanismOrigin |
P146662
|
FINISHED |
| Object | England |
—
|
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: England | Statement: [Torre Monumental, hasClockMechanismOrigin, England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClockMechanismOrigin Context triple: [Torre Monumental, hasClockMechanismOrigin, England]
-
A.
hasClockMechanismDate
Indicates that an entity has an associated date specifying when its clock mechanism was created, installed, or became effective.
-
B.
hasClockMechanismSimilarTo
Indicates that one entity’s clock mechanism is similar in structure, function, or design to that of another entity.
-
C.
clockMechanismOrigin
chosen
Indicates that one entity is the source, creator, or originating context of a particular clock mechanism associated with another entity.
-
D.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
-
E.
clockMechanism
Indicates that one entity functions as the internal mechanism or movement that drives the operation of a clock.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 28, 2026, 1:24 a.m.