Triple
T6551805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galen |
E151145
|
entity |
| Predicate | textsPreservedIn |
P21692
|
FINISHED |
| Object | Greek manuscripts |
—
|
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: Greek manuscripts | Statement: [Galen, textsPreservedIn, Greek manuscripts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textsPreservedIn Context triple: [Galen, textsPreservedIn, Greek manuscripts]
-
A.
workPreservedIn
chosen
Indicates that a work is maintained, stored, or archived within a particular medium, collection, or repository so that it remains accessible over time.
-
B.
textsIncludedIn
Indicates that certain texts are contained within, or form a subset of, a larger collection or body of texts.
-
C.
notableText
Indicates that a particular piece of text is especially significant, prominent, or worthy of attention in relation to the associated entity or context.
-
D.
preservedExample
Indicates that an example instance has been kept intact or maintained in its original state for future reference or use.
-
E.
hasHistoricalText
Indicates that an entity is associated with a historical written document or record describing it or its past.
- 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:51 p.m.