Triple
T33911004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catwoman story pack |
E869310
|
entity |
| Predicate | contentAccessMethod |
P5872
|
FINISHED |
| Object | download code |
—
|
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: download code | Statement: [Catwoman story pack, contentAccessMethod, download code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentAccessMethod Context triple: [Catwoman story pack, contentAccessMethod, download code]
-
A.
contentAccess
Indicates that one entity is permitted to retrieve, view, or otherwise use the content provided or controlled by another entity.
-
B.
accessMethod
chosen
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
C.
contentProvider
Indicates that one entity serves as the source or supplier of content (such as media, information, or data) for another entity.
-
D.
contentIs
Indicates that one entity serves as, or is equivalent to, the content contained within another entity.
-
E.
accessProtocol
Indicates the method or rules by which one entity is allowed to access or communicate with another entity or resource.
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:48 a.m.