Triple
T4028865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megadodo Publications |
E83657
|
entity |
| Predicate | inUniverseTechnology |
P19268
|
FINISHED |
| Object | electronic book production |
—
|
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: electronic book production | Statement: [Megadodo Publications, inUniverseTechnology, electronic book production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseTechnology Context triple: [Megadodo Publications, inUniverseTechnology, electronic book production]
-
A.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
B.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
C.
technologyField
chosen
Indicates the area or domain of technology in which an entity is involved, specialized, or categorized.
-
D.
technologyBasis
Indicates that one entity is founded on, enabled by, or fundamentally relies upon the technology provided or represented by another entity.
-
E.
technologyIncludes
Indicates that one technology encompasses, contains, or incorporates another technology as part of its components, features, or implementation.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaf066b08190afbb4a18ddc8d67e |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.