Triple
T8836165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human towers (castells) |
E210270
|
entity |
| Predicate | typicalHeightRange |
P573
|
FINISHED |
| Object | 6 to 10 levels |
—
|
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: 6 to 10 levels | Statement: [Human towers (castells), typicalHeightRange, 6 to 10 levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHeightRange Context triple: [Human towers (castells), typicalHeightRange, 6 to 10 levels]
-
A.
typicalHeight
chosen
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
B.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
C.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
D.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
E.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
- 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_69ca8388549c819095fd94eadefbb007 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6069ad7881909e31010e73e26f91 |
completed | April 1, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:47 p.m.