Triple
T24842514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antipascha |
E621652
|
entity |
| Predicate | keyExclamation |
P157403
|
FINISHED |
| Object | My Lord and my God |
—
|
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: My Lord and my God | Statement: [Antipascha, keyExclamation, My Lord and my God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyExclamation Context triple: [Antipascha, keyExclamation, My Lord and my God]
-
A.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
B.
keys
Indicates that one entity serves as a key (or set of keys) that can open, access, or control another entity.
-
C.
keyExercise
Indicates that an exercise is a primary or essential component within a larger training, practice, or instructional context.
-
D.
keySymbol
Indicates that one entity serves as the symbolic representation or notation used to denote another entity as a key.
-
E.
keySaying
Indicates that an entity is a notable or characteristic saying, phrase, or quotation associated with another entity.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f4303fad6c8190844f069164f0904d |
completed | May 1, 2026, 4:46 a.m. |
Created at: April 18, 2026, 5:19 a.m.