Triple
T37553864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gehennas |
E933647
|
entity |
| Predicate | requiresSize |
P176615
|
FINISHED |
| Object | 40 players |
—
|
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: 40 players | Statement: [Gehennas, requiresSize, 40 players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSize Context triple: [Gehennas, requiresSize, 40 players]
-
A.
sizeRequired
chosen
Indicates that a particular size or dimension is needed or must be met for something to be suitable, valid, or functional.
-
B.
checkSize
Indicates that an entity evaluates or verifies whether another entity’s size meets certain criteria or constraints.
-
C.
hasSize
Indicates that one entity possesses a particular physical magnitude or extent, such as length, volume, or overall dimensions.
-
D.
desiredSizeIndicates
Indicates that one entity specifies or reflects the preferred or intended size of another entity.
-
E.
shapeRequirement
Indicates that one entity imposes or specifies a required shape or geometric form that another entity must conform to.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a007338002081908cb6340d65ff86d5 |
completed | May 10, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_6a0072a137ac8190a7debeb28e738e03 |
completed | May 10, 2026, 11:57 a.m. |
Created at: May 3, 2026, 4:17 p.m.