Triple
T6288060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annals |
E140947
|
entity |
| Predicate | survivingBooks |
P47754
|
FINISHED |
| Object | Books 1–4 |
—
|
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: Books 1–4 | Statement: [Annals, survivingBooks, Books 1–4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingBooks Context triple: [Annals, survivingBooks, Books 1–4]
-
A.
booksSurvivingCompletely
chosen
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.
survivingSources
Indicates that there exist remaining or extant sources (e.g., documents, records, artifacts) that attest to or provide evidence about the subject.
-
E.
survivesIn
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064182f60819093a8313e1dbf2763 |
completed | March 22, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69c060df0d8881908215575862ef6831 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:26 p.m.