Triple
T23648947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Shrovetide Football |
E584115
|
entity |
| Predicate | ballBuoyancy |
P135947
|
FINISHED |
| Object | designed to float in water |
—
|
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: designed to float in water | Statement: [Royal Shrovetide Football, ballBuoyancy, designed to float in water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballBuoyancy Context triple: [Royal Shrovetide Football, ballBuoyancy, designed to float in water]
-
A.
buoyancyStructure
Indicates a structural relationship where one entity provides buoyant support or flotation capability for another.
-
B.
ballBehavior
chosen
Indicates how a ball acts or responds under certain conditions or interactions.
-
C.
haveBuoyancyAdaptation
Indicates that an entity possesses adaptations or mechanisms that enable it to control or maintain its buoyancy in a fluid environment.
-
D.
usesBallShape
Indicates that one entity employs or incorporates a ball-like (spherical) shape in its form, design, or operation.
-
E.
ballType
Indicates the specific category or kind of ball associated with an entity.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b287606881909926de5efd882a76 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.