Triple
T11547208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torghast, Tower of the Damned |
E273802
|
entity |
| Predicate | minPlayers |
P9344
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Torghast, Tower of the Damned, minPlayers, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minPlayers Context triple: [Torghast, Tower of the Damned, minPlayers, 1]
-
A.
typicalNumberOfPlayers
Indicates the usual or standard number of players involved in participating in an activity or game.
-
B.
minimumNumberOfGames
Indicates the smallest required count of games that must be played or satisfied in a given context or constraint.
-
C.
intendedPlayers
Indicates the players for whom something (such as a game, item, or activity) is designed or meant to be used.
-
D.
minimumNumberOfMembers
chosen
Indicates the smallest allowable or required number of members that must be present or involved in a given context or group.
-
E.
minimumPlateAppearancesRequirement
Indicates that there is a minimum number of plate appearances a player must have to qualify for a particular statistic, ranking, or eligibility condition.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e3ad548190b2c88332f5d919bd |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.