Triple
T28722652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gregory–Aland 𝔓46 |
E730135
|
entity |
| Predicate | hasWordDivision |
P184366
|
FINISHED |
| Object | scriptio continua |
—
|
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: scriptio continua | Statement: [Gregory–Aland 𝔓46, hasWordDivision, scriptio continua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWordDivision Context triple: [Gregory–Aland 𝔓46, hasWordDivision, scriptio continua]
-
A.
textualDivisionOf
Indicates that one text segment functions as a structural subdivision (such as a chapter, section, or paragraph) within another text.
-
B.
hasVerseDivision
Indicates that a text or passage is organized into or associated with specific verse divisions.
-
C.
isDividedFrom
Indicates that one entity is separated or partitioned from another, typically by a boundary, barrier, or dividing line.
-
D.
hasHyphenation
Indicates that one entity specifies or provides the hyphenated form or hyphenation pattern of another entity.
-
E.
hasWordFormation
Indicates that one linguistic unit is formed or derived from another through a specific word-formation process (such as compounding, derivation, or affixation).
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: April 28, 2026, 5:54 a.m.