Triple
T33633703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine rite |
E861633
|
entity |
| Predicate | hasFast |
P194266
|
FINISHED |
| Object | Great Lent |
—
|
NE NERFINISHED |
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: Great Lent | Statement: [Byzantine rite, hasFast, Great Lent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFast Context triple: [Byzantine rite, hasFast, Great Lent]
-
A.
containsFast
Indicates that one entity includes or holds another entity in a way that allows rapid or high-speed access, interaction, or processing.
-
B.
hasFastLines
Indicates that the subject possesses or is associated with lines that operate or move at a high speed.
-
C.
hasFastInMonth
Indicates that an entity observes or performs a fast during a specified month.
-
D.
hasHighSpeedPotential
Indicates that an entity possesses the capability or conditions to achieve or sustain a high rate of speed, even if it is not currently doing so.
-
E.
isFastGrowing
Indicates that an entity increases in size, quantity, or impact at a rapid or above-average rate over time.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
| PDg | Predicate description generation | batch_69fd68ab21a0819096bfc4a8c14851ad |
completed | May 8, 2026, 4:38 a.m. |
Created at: May 1, 2026, 1:41 a.m.