Triple
T37874486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elder Rifts |
E944682
|
entity |
| Predicate | supportsPartySizeUpTo |
P26049
|
FINISHED |
| Object | 4 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: 4 players | Statement: [Elder Rifts, supportsPartySizeUpTo, 4 players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPartySizeUpTo Context triple: [Elder Rifts, supportsPartySizeUpTo, 4 players]
-
A.
seatsForParty
chosen
Indicates that a seating arrangement or capacity is designated to accommodate a specific party or group.
-
B.
party1Seats
Indicates the number of seats held or allocated to the first party in a multi-party context.
-
C.
party2Seats
Indicates the number of seats held or allocated to the second party in a given context (such as an election or governing body).
-
D.
suitableForLargeGroups
Indicates that something can comfortably accommodate or is appropriate for use by a relatively high number of people at the same time.
-
E.
party6Seats
Indicates the number of seats held or allocated to a sixth party in a multi-party context.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.