Triple
T17141037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Fountain |
E415961
|
entity |
| Predicate | hasHeightClaim |
P64481
|
FINISHED |
| Object | one of the highest gravity-fed fountains in the world |
—
|
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: one of the highest gravity-fed fountains in the world | Statement: [Emperor Fountain, hasHeightClaim, one of the highest gravity-fed fountains in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeightClaim Context triple: [Emperor Fountain, hasHeightClaim, one of the highest gravity-fed fountains in the world]
-
A.
heightClaim
chosen
Indicates that one entity asserts or reports a specific height for another entity (or itself).
-
B.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
C.
hasSignificantHeight
Indicates that one entity’s height is notably large or substantial relative to a given standard or to other entities.
-
D.
estimatedHeadHeightInMeters
Indicates the estimated vertical height of a person's head, measured in meters.
-
E.
heightRestriction
Indicates that there is a limit or constraint on how tall an entity is allowed or required to be in a given context.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2d44a508190a3a149c3a64957f5 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.