Triple
T30108109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acts and Catholic Epistles in Byzantine textform |
E765185
|
entity |
| Predicate | hasCriticalApparatus |
P180047
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Acts and Catholic Epistles in Byzantine textform, hasCriticalApparatus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCriticalApparatus Context triple: [Acts and Catholic Epistles in Byzantine textform, hasCriticalApparatus, yes]
-
A.
hasTypeOfApparatus
Indicates that one entity is associated with, or utilizes, a specific kind or category of apparatus.
-
B.
hasEmergencyTransport
Indicates that an entity provides, is equipped with, or has access to emergency transportation services or vehicles.
-
C.
hasArrestingGear
Indicates that an entity is equipped with a system or mechanism used to rapidly decelerate and stop another entity, typically during landing or capture.
-
D.
hasCrane
Indicates that an entity possesses, includes, or is equipped with a crane.
-
E.
hasEmergencySystems
Indicates that the subject is equipped with or includes systems designed to detect, respond to, or manage emergency situations.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 29, 2026, 7:10 p.m.