Triple
T31047704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Knot City |
E791172
|
entity |
| Predicate | hasNPC |
P170697
|
FINISHED |
| Object | Port Knot City terminal manager |
—
|
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: Port Knot City terminal manager | Statement: [Port Knot City, hasNPC, Port Knot City terminal manager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNPC Context triple: [Port Knot City, hasNPC, Port Knot City terminal manager]
-
A.
hasCreature
Indicates that one entity possesses, contains, or is associated with a particular creature.
-
B.
supportsNPCs
Indicates that an entity provides functionality or compatibility for non-player characters (NPCs) within a system or environment.
-
C.
representsInNPC
Indicates that one entity serves as a non-player character (NPC) representation or avatar of another entity within a system or context.
-
D.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
E.
hasMob
Indicates that an entity possesses, controls, or is associated with a particular mob or group of mobile agents.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953db334819083dcdfcf1e3d97f2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 29, 2026, 9 p.m.