Triple
T4578789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Week |
E101803
|
entity |
| Predicate | typicalMethod |
P12146
|
FINISHED |
| Object | contemplation of Gospel scenes |
—
|
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: contemplation of Gospel scenes | Statement: [Third Week, typicalMethod, contemplation of Gospel scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMethod Context triple: [Third Week, typicalMethod, contemplation of Gospel scenes]
-
A.
typicalFunction
Indicates that something serves as the usual or characteristic function or role of an entity.
-
B.
method
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
C.
typicalPractice
chosen
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
-
D.
notableMethod
Indicates that a particular method, technique, or approach is especially significant, recognized, or noteworthy in relation to the associated entity.
-
E.
typicalRegister
Indicates the usual or most common linguistic register (e.g., formal, informal, technical) in which something—such as a word, expression, or communication—is typically used.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd58e2a1808190be4582d5b3003d6c |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.