Triple
T1101207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munttoren |
E24383
|
entity |
| Predicate | hasClockSince |
P24142
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Munttoren, hasClockSince, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClockSince Context triple: [Munttoren, hasClockSince, 17th century]
-
A.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
-
B.
hasTimeStart
Indicates that an event, process, or state begins at a specific point in time.
-
C.
usesClockAdvance
Indicates that one entity performs an action or operates a process by advancing a clock or time reference forward.
-
D.
observedSince
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
-
E.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9c079f48190a0e0ddda182f7a01 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b745ef3481909a7ce4647c8567b3 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8f1097881908932d7eea4331917 |
completed | March 1, 2026, 10:08 p.m. |
Created at: March 1, 2026, 7:43 p.m.