Triple
T8836166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human towers (castells) |
E210270
|
entity |
| Predicate | canReachHeight |
P84922
|
FINISHED |
| Object | up to 10 levels or more |
—
|
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: up to 10 levels or more | Statement: [Human towers (castells), canReachHeight, up to 10 levels or more]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canReachHeight Context triple: [Human towers (castells), canReachHeight, up to 10 levels or more]
-
A.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
B.
hasStaircaseToSummit
Indicates that there exists a staircase providing a direct route or access from a lower point to the summit of something.
-
C.
climbedBy
Indicates that something is ascended or scaled by an agent or entity.
-
D.
climbedInRange
Indicates that an entity’s climbing activity occurred within a specified range of values, such as time, distance, or elevation.
-
E.
hasClimbSide
Indicates that one entity has a particular side or surface that is suitable or designated for climbing.
- 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_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. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:47 p.m.