Triple
T38592131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarab Wall |
E932477
|
entity |
| Predicate | statusInModernGame |
P183590
|
FINISHED |
| Object | permanently open on most realms |
—
|
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: permanently open on most realms | Statement: [Scarab Wall, statusInModernGame, permanently open on most realms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInModernGame Context triple: [Scarab Wall, statusInModernGame, permanently open on most realms]
-
A.
lawsOfTheGameStatus
Indicates the status or condition of the applicable rules or laws governing how a game is played.
-
B.
inGameStatus
Indicates the current state or condition of an entity within the context of a game (e.g., active, paused, eliminated).
-
C.
gameModeStatus
chosen
Indicates the current state or condition of a game mode, such as whether it is active, available, or in a particular operational phase.
-
D.
statusInModernUsage
Indicates how the usage or relevance of something is currently regarded or applied in contemporary contexts.
-
E.
preModernStatus
Indicates that an entity held a particular status, condition, or classification during a pre-modern historical period.
- 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_6a002249ee388190a9501ee7630dc658 |
completed | May 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_6a002189273881909b6b687e2d61f5b1 |
completed | May 10, 2026, 6:11 a.m. |
Created at: May 3, 2026, 4:32 p.m.