Triple
T36937280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shi No Numa |
E913652
|
entity |
| Predicate | mapObjective |
P186710
|
FINISHED |
| Object | survive endless waves of zombies |
—
|
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: survive endless waves of zombies | Statement: [Shi No Numa, mapObjective, survive endless waves of zombies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapObjective Context triple: [Shi No Numa, mapObjective, survive endless waves of zombies]
-
A.
expeditionObjective
Indicates the primary goal or purpose that an expedition is intended to achieve.
-
B.
mapLocation
Indicates a relationship where an entity is associated with a specific position or area on a map.
-
C.
mapUse
Indicates a relationship where one entity uses, applies, or employs a map (or mapping) to perform an action or achieve a purpose.
-
D.
mapSystem
Indicates a relationship where one system is associated with or represented by a specific map or mapping framework.
-
E.
mappingTarget
Indicates that one entity serves as the destination or result of a mapping defined from 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.