Triple
T29647940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foundation |
E756054
|
entity |
| Predicate | publicCover |
P194658
|
FINISHED |
| Object | compilation of the Encyclopedia Galactica |
—
|
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: compilation of the Encyclopedia Galactica | Statement: [Foundation, publicCover, compilation of the Encyclopedia Galactica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicCover Context triple: [Foundation, publicCover, compilation of the Encyclopedia Galactica]
-
A.
usedCover
Indicates that one entity employed another entity as a protective or concealing cover in a given context.
-
B.
formerCover
Indicates that one entity previously served as the cover (e.g., protective or outer layer) for another entity but no longer does so.
-
C.
isCover
Indicates that one entity functions as a protective or concealing layer over another entity.
-
D.
cover
Indicates that one entity extends over, conceals, protects, or provides a surface or layer for another entity.
-
E.
coverText
Indicates that one text serves as the cover or front-facing textual representation for another work or resource.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
| PDg | Predicate description generation | batch_69fd7fd9be2881908a7f00e0e8822de8 |
completed | May 8, 2026, 6:16 a.m. |
Created at: April 28, 2026, 6:50 p.m.