Triple
T14470069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Elephant |
E358814
|
entity |
| Predicate | hasRevelationOrder |
P48135
|
FINISHED |
| Object | 19 |
—
|
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: 19 | Statement: [The Elephant, hasRevelationOrder, 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevelationOrder Context triple: [The Elephant, hasRevelationOrder, 19]
-
A.
hasRevelationPeriod
Indicates the time span or phase during which a revelation, disclosure, or unveiling of something occurs or is valid.
-
B.
hasRevelationType
Indicates the specific kind or category of revelation associated with an entity or event.
-
C.
orderOfRevelation
chosen
Indicates the sequence in which multiple related items, events, or pieces of information are revealed or disclosed.
-
D.
hasModeOfRevelation
Indicates the manner or channel through which something is revealed, communicated, or made known.
-
E.
receivesRevelation
Indicates that one entity is the recipient of a divine, supernatural, or otherwise profound revelation originating from another source.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91f969788190a5114f92d7159aae |
completed | April 14, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.