Triple
T6605729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Place de la Palud |
E149111
|
entity |
| Predicate | clockShows |
P71997
|
FINISHED |
| Object | historical scenes of Lausanne |
—
|
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: historical scenes of Lausanne | Statement: [Place de la Palud, clockShows, historical scenes of Lausanne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clockShows Context triple: [Place de la Palud, clockShows, historical scenes of Lausanne]
-
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.
clockDiameter
Indicates that one entity specifies or measures the diameter of a clock associated with another entity.
-
D.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
-
E.
clockMechanismEngineer
Indicates that one entity is an engineer who designs, builds, or maintains clock mechanisms for another entity or context.
- 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_69c687eaa7508190bb58ce2aa02039b3 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acfd17388190bd0bb8b2371e7df1 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 1:56 p.m.