Triple
T13671146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feast (Roman Rite, ordinary form) |
E327750
|
entity |
| Predicate | normallyWithout |
P13714
|
FINISHED |
| Object | Creed |
—
|
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: Creed | Statement: [Feast (Roman Rite, ordinary form), normallyWithout, Creed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: normallyWithout Context triple: [Feast (Roman Rite, ordinary form), normallyWithout, Creed]
-
A.
notTypically
Indicates that the referenced situation, behavior, or relationship does not usually or normally occur under standard or expected conditions.
-
B.
ordinary
Indicates that something or someone is typical, usual, or not special or exceptional in the relevant context.
-
C.
ordinaryMayBe
Indicates that something is typically or commonly allowed, possible, or permitted under normal circumstances.
-
D.
nonPostNominal
Indicates that the related element does not appear in a post-nominal position (i.e., it does not follow the noun it modifies or relates to).
-
E.
typicallyLack
chosen
Indicates that one entity is characteristically or usually without, or does not possess, another entity or attribute.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc6599c248190b7f134b5b9947a23 |
completed | April 12, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.