Triple
T7810266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Testament Greek tradition |
E180660
|
entity |
| Predicate | includesCorpus |
P67055
|
FINISHED |
| Object | Gospels |
—
|
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: Gospels | Statement: [New Testament Greek tradition, includesCorpus, Gospels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCorpus Context triple: [New Testament Greek tradition, includesCorpus, Gospels]
-
A.
hasPartOfCorpus
chosen
Indicates that one entity constitutes a component or segment of the overall corpus associated with another entity.
-
B.
corpus
Indicates that an entity is a collection or body of texts, documents, or linguistic data used as a unified set for analysis or reference.
-
C.
hasNotableCorpus
Indicates that an entity possesses a significant, well-recognized body of work, texts, or collected materials associated with it.
-
D.
hasCorpusType
Indicates the type or category of corpus associated with an entity (e.g., text, speech, multimodal).
-
E.
hasLimitedCorpus
Indicates that the associated entity possesses only a small or restricted set of available data, texts, or examples for use or analysis.
- 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_69ca827f6f148190beca4e245b993506 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78bb4b08190b2b3b51c5a0a033c |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:37 p.m.