Triple
T10740350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nail in the Pale |
E253307
|
entity |
| Predicate | refersToHeightCharacteristic |
P90499
|
FINISHED |
| Object | tall monument |
—
|
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: tall monument | Statement: [The Nail in the Pale, refersToHeightCharacteristic, tall monument]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToHeightCharacteristic Context triple: [The Nail in the Pale, refersToHeightCharacteristic, tall monument]
-
A.
heightReference
Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
-
B.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
C.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
D.
heightDescription
chosen
Indicates how tall an entity is, typically expressed in descriptive or qualitative terms rather than a precise measurement.
-
E.
heightInCentimetres
Indicates the numerical value of an entity’s height measured in centimetres.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71043106c819091939950f532eda5 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.