Triple
T38589151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lower Spire |
E932412
|
entity |
| Predicate | designedForGroupSize |
P75538
|
FINISHED |
| Object | 10 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: 10 players | Statement: [The Lower Spire, designedForGroupSize, 10 players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForGroupSize Context triple: [The Lower Spire, designedForGroupSize, 10 players]
-
A.
typicalGroupSize
chosen
Indicates the usual or characteristic number of individuals that typically form a group in this context.
-
B.
suitableForLargeGroups
Indicates that something can comfortably accommodate or is appropriate for use by a relatively high number of people at the same time.
-
C.
typicalGroupSizeRange
Indicates the usual minimum and maximum number of individuals that typically occur together in a group for the given entity.
-
D.
sizeOfGroup
Indicates the number of individuals or elements that make up a particular group.
-
E.
airGroupSize
Indicates the number of units or elements grouped together in an air-related context (such as aircraft in a formation or air assets in an operation).
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffac35ac5481908b6bdfd5bbe8c76e |
completed | May 9, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69ffabbfd2548190964c851496bbbaee |
completed | May 9, 2026, 9:48 p.m. |
Created at: May 3, 2026, 4:32 p.m.