Triple
T10113685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nineteen Day Feast |
E218302
|
entity |
| Predicate | functionForAssembly |
P92275
|
FINISHED |
| Object | channel for feedback from believers |
—
|
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: channel for feedback from believers | Statement: [Nineteen Day Feast, functionForAssembly, channel for feedback from believers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionForAssembly Context triple: [Nineteen Day Feast, functionForAssembly, channel for feedback from believers]
-
A.
hasAssembler
Indicates that one entity is responsible for assembling, putting together, or constructing another entity.
-
B.
hasAssembly
Indicates that an entity is composed of, or includes, one or more component parts assembled into a whole.
-
C.
hasAssemblyType
Indicates that an entity is associated with or classified by a specific type or method of assembly.
-
D.
hasAssemblyLineFor
Indicates that one entity operates or contains an assembly line specifically used to produce, process, or assemble another entity.
-
E.
assemblyRequired
Indicates that the associated item or components must be put together or constructed before they can be used.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd15ed28081909a812e0634799ef8 |
completed | April 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8f869c8190a82ad040993e0244 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9:04 p.m.