Triple
T9362503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1937 Columbus Platform |
E225313
|
entity |
| Predicate | positionOnRevelation |
P12429
|
FINISHED |
| Object | affirmed ongoing, progressive revelation |
—
|
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: affirmed ongoing, progressive revelation | Statement: [1937 Columbus Platform, positionOnRevelation, affirmed ongoing, progressive revelation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnRevelation Context triple: [1937 Columbus Platform, positionOnRevelation, affirmed ongoing, progressive revelation]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
viewOnRevelation
chosen
Indicates the stance or interpretation an entity holds regarding the nature, source, or authority of divine revelation.
-
C.
positionInShow
Indicates the specific order or placement an entity occupies within a show, series, or sequence of performances or episodes.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
positionOnIdentity
Indicates a stance, view, or opinion that an entity holds regarding identity-related issues or characteristics.
- 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_69ca842bdd648190904131d58620d448 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd503ca7308190818f27f1faf94a53 |
completed | April 1, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6abb8c81908c7a2f4ee92cc949 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:42 p.m.