Triple
T37514522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruined Temple |
E932599
|
entity |
| Predicate | intendedForPlayers |
P61189
|
FINISHED |
| Object | Mid-level characters |
—
|
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: Mid-level characters | Statement: [Ruined Temple, intendedForPlayers, Mid-level characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedForPlayers Context triple: [Ruined Temple, intendedForPlayers, Mid-level characters]
-
A.
intendedPlayers
chosen
Indicates the players for whom something (such as a game, item, or activity) is designed or meant to be used.
-
B.
givesToPlayers
Indicates that one entity transfers or provides something to one or more player entities.
-
C.
intendedForSeries
Indicates that something is designed, created, or designated to be used within or as part of a particular series.
-
D.
intendedForPerformanceBy
Indicates that something (such as a work, role, or piece) is designed or meant to be performed by a particular performer or type of performer.
-
E.
intendedTargets
Indicates that an action, message, or object is specifically directed toward or meant to affect particular target entities.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.