Triple
T14771686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Power |
E347148
|
entity |
| Predicate | originallyRevealedIn |
P26941
|
FINISHED |
| Object | 7th century CE |
—
|
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: 7th century CE | Statement: [The Power, originallyRevealedIn, 7th century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyRevealedIn Context triple: [The Power, originallyRevealedIn, 7th century CE]
-
A.
originallyAppearedOn
Indicates the original source or platform where something (such as a work, content, or item) was first published, released, or made available.
-
B.
isRevealedIn
Indicates that something becomes known, disclosed, or made apparent within a particular context, medium, or situation.
-
C.
originallyReleasedOn
Indicates the date or platform on which something (such as a work, product, or media item) was first made publicly available.
-
D.
unveiledBy
Indicates that something (such as an object, artwork, or project) was formally revealed or presented to the public by a particular agent or entity.
-
E.
timeOfFirstRevelation
chosen
Indicates the specific time at which the first revelation or initial disclosure of something occurred.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec81334e08190a77d760e507d00ed |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.