Triple
T37471097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fracture Chambers |
E931153
|
entity |
| Predicate | designedForContentType |
P640
|
FINISHED |
| Object | PvE |
—
|
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: PvE | Statement: [Fracture Chambers, designedForContentType, PvE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForContentType Context triple: [Fracture Chambers, designedForContentType, PvE]
-
A.
describesContentType
Indicates that one entity specifies or characterizes the type or category of content associated with another entity.
-
B.
governsContentType
Indicates that one entity defines or controls the rules, behavior, or handling associated with a particular content type.
-
C.
hasContentType
chosen
Indicates that an entity is associated with or classified by a specific type of content.
-
D.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
E.
producedContentType
Indicates that an entity has created or generated content of a specified type or format.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
Created at: May 3, 2026, 4:17 p.m.