Triple
T28824632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Photinus of Sirmium |
E727867
|
entity |
| Predicate | doctrineDescribedAs |
P15802
|
FINISHED |
| Object | Photinianism |
—
|
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: Photinianism | Statement: [Photinus of Sirmium, doctrineDescribedAs, Photinianism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrineDescribedAs Context triple: [Photinus of Sirmium, doctrineDescribedAs, Photinianism]
-
A.
doctrineRefined
Indicates that an existing doctrine has been further developed, clarified, or improved in its formulation or application.
-
B.
describedFrom
Indicates that something is characterized, explained, or defined based on information, perspective, or features originating from a particular source or reference point.
-
C.
doctrineExplainedBy
chosen
Indicates that an explanation or interpretation is provided for a particular doctrine by a specified source or agent.
-
D.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
E.
describes
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:35 a.m.