Triple
T36732343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matthew–Luke–Mark |
E907373
|
entity |
| Predicate | viewOnQSource |
P45238
|
FINISHED |
| Object | does not require Q |
—
|
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: does not require Q | Statement: [Matthew–Luke–Mark, viewOnQSource, does not require Q]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnQSource Context triple: [Matthew–Luke–Mark, viewOnQSource, does not require Q]
-
A.
viewOnSources
chosen
Indicates that an entity’s perspective, opinion, or interpretation is based on, derived from, or informed by specific source materials.
-
B.
viewOnState
Indicates that one entity holds or expresses a particular opinion, stance, or perspective regarding a specific state or condition.
-
C.
viewIs
Indicates that one entity is a visual representation or perspective of another entity.
-
D.
viewOnCustom
Indicates that one entity is being viewed, accessed, or displayed through a customized or user-defined view associated with another entity.
-
E.
viewOnSin
Indicates a person's stance, opinion, or doctrinal position regarding what constitutes sin or sinful behavior.
- 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 3, 2026, 4:12 p.m.