Triple
T38634513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rust (Call of Duty: Modern Warfare 2 map) |
E937541
|
entity |
| Predicate | spawnBehavior |
P191950
|
FINISHED |
| Object | frequent close spawns |
—
|
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: frequent close spawns | Statement: [Rust (Call of Duty: Modern Warfare 2 map), spawnBehavior, frequent close spawns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spawnBehavior Context triple: [Rust (Call of Duty: Modern Warfare 2 map), spawnBehavior, frequent close spawns]
-
A.
spawns
Indicates that one entity generates, creates, or gives rise to another entity, often as an origin or source.
-
B.
spaceBehavior
Indicates how an entity behaves, operates, or is arranged within a given space or spatial context.
-
C.
trailBehavior
Indicates how an entity behaves, moves, or leaves traces along a path or trajectory over time.
-
D.
spawnReason
Indicates the cause or triggering condition that led to an entity or object being created or appearing.
-
E.
enemyBehavior
Indicates how an enemy entity acts or responds within a given context, such as its tactics, reactions, or decision patterns toward others.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69fcef636dfc819085cf91323f2e4edd |
completed | May 7, 2026, 8 p.m. |
Created at: May 3, 2026, 4:32 p.m.