Triple
T29118982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encyclopedia Foundation |
E737123
|
entity |
| Predicate | coverStoryFor |
P145425
|
FINISHED |
| Object | Foundation |
—
|
NE NERFINISHED |
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: Foundation | Statement: [Encyclopedia Foundation, coverStoryFor, Foundation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverStoryFor Context triple: [Encyclopedia Foundation, coverStoryFor, Foundation]
-
A.
usesCoverStory
chosen
Indicates that one entity employs a false or misleading explanation or narrative to conceal its true intentions, identity, or activities from another entity.
-
B.
coverText
Indicates that one text serves as the cover or front-facing textual representation for another work or resource.
-
C.
coversArticles
Indicates that one entity provides coverage or reporting about the articles associated with another entity.
-
D.
cover
Indicates that one entity extends over, conceals, protects, or provides a surface or layer for another entity.
-
E.
locationCoverStory
Indicates that a particular location is used as a cover or front to conceal the true nature, purpose, or activities associated with something or someone.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 28, 2026, 11:24 a.m.