Triple
T35009204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planescape |
E1009900
|
entity |
| Predicate | gameLine |
P181993
|
FINISHED |
| Object | Planescape Campaign Setting boxed set |
—
|
NE NERFINISHED |
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: Planescape Campaign Setting boxed set | Statement: [Planescape, gameLine, Planescape Campaign Setting boxed set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameLine Context triple: [Planescape, gameLine, Planescape Campaign Setting boxed set]
-
A.
notableGameLine
Indicates that a particular line of dialogue or text is especially notable or significant within a game.
-
B.
yardLine
Indicates the specific position on a football field, measured in yards from a reference goal line, where a play or event occurs.
-
C.
gamePlayed
Indicates that a particular game is or was played by an entity (such as a person, team, or group) during a specific event or time.
-
D.
game4Winner
Indicates which participant or side is the winner of the fourth game in a series or match.
-
E.
testingLine
Indicates that one entity is being used as a test or trial version of a line, sequence, or boundary associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.