Triple
T32098983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theologica |
E819793
|
entity |
| Predicate | writtenByPersonFrom |
P144320
|
FINISHED |
| Object | Constantinople |
—
|
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: Constantinople | Statement: [Theologica, writtenByPersonFrom, Constantinople]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenByPersonFrom Context triple: [Theologica, writtenByPersonFrom, Constantinople]
-
A.
mainlyWrittenBy
Indicates that the primary authorship or main writing responsibility for something is attributed to a particular entity.
-
B.
writtenByFormer
Indicates that something was written by an individual who previously held a particular role, position, or status.
-
C.
writtenByScholarFrom
chosen
Indicates that something was written by a scholar who originates from or is affiliated with a specified place or region.
-
D.
producedPerson
Indicates that one entity created, generated, or brought into existence the person referenced by the other entity.
-
E.
createdByWritersOf
Indicates that something (such as a work, character, or concept) was created by the writers of a specified work or series.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b647a7a88190aeef1b9b1e2d5f3b |
completed | May 3, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:26 a.m.