Triple
T6598285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carillon generating station |
E148530
|
entity |
| Predicate | hasMaximumHead |
P55323
|
FINISHED |
| Object | about 17 metres |
—
|
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: about 17 metres | Statement: [Carillon generating station, hasMaximumHead, about 17 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumHead Context triple: [Carillon generating station, hasMaximumHead, about 17 metres]
-
A.
hasMaximumValue
Indicates that one value in a set is the greatest or highest possible according to a specified criterion.
-
B.
hasMaximumThickness
chosen
Indicates that an entity possesses a specified upper limit on its thickness.
-
C.
isMaximumWhen
Indicates that a quantity or function reaches its greatest possible value under specified conditions or at a particular point.
-
D.
hasHeadCount
Indicates that an entity is associated with a specific number of individuals, typically representing the size or count of people (or similar units) related to it.
-
E.
hasMaximumGrade
Indicates that an entity possesses the highest possible grade or score within a defined grading or evaluation 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_69c687e7b8688190811ffee72e096468 |
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. |
Created at: March 27, 2026, 1:56 p.m.