Triple
T11542235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Undercity |
E273699
|
entity |
| Predicate | startingAreaFor |
P39115
|
FINISHED |
| Object | Forsaken player 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: Forsaken player characters | Statement: [Undercity, startingAreaFor, Forsaken player characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingAreaFor Context triple: [Undercity, startingAreaFor, Forsaken player characters]
-
A.
hasStartingArea
chosen
Indicates that an entity is associated with, or begins from, a specific initial area or region.
-
B.
startingPark
Indicates that an entity begins or initiates its activity, route, or presence from a specified park.
-
C.
spawningLocation
Indicates the place or environment where an entity originates, appears, or is generated.
-
D.
landingArea
Indicates that a location or surface serves as a designated area where something (such as an aircraft, object, or person) can land.
-
E.
navigationArea
Indicates that a specified region or space is designated for movement, routing, or pathfinding within an environment.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e09eec8190894069d86b79183d |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.