Triple
T18283555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De lingua Latina |
E437922
|
entity |
| Predicate | booksSurvivingPartially |
P131176
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [De lingua Latina, booksSurvivingPartially, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: booksSurvivingPartially Context triple: [De lingua Latina, booksSurvivingPartially, 1]
-
A.
booksSurvivingCompletely
Indicates that the books in question have remained fully intact and unchanged, with no parts lost or damaged.
-
B.
booksSurvivingRange
Indicates that the books in question remained extant or available throughout a specified range of time or conditions.
-
C.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
D.
survivalStoryChronicledIn
Indicates that an account of surviving a dangerous or life-threatening situation is documented or recorded within a particular medium or work.
-
E.
survivorsJourney
Indicates the ongoing process or path a survivor takes as they cope with, adapt to, and move forward from a traumatic or life-threatening experience.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500f7ff088190933bb8f403ce7f9c |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:35 a.m.