Triple
T3306968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ab Urbe Condita |
E69473
|
entity |
| Predicate | survivingPortions |
P47939
|
FINISHED |
| Object | continuous books 1–10 |
—
|
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: continuous books 1–10 | Statement: [Ab Urbe Condita, survivingPortions, continuous books 1–10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingPortions Context triple: [Ab Urbe Condita, survivingPortions, continuous books 1–10]
-
A.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
B.
survivesIn
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
-
C.
survivesAs
Indicates that one entity continues to exist or persist in place of, or after the end or transformation of, another entity.
-
D.
survivingStructure
Indicates that a structure continues to exist or remain intact after a potentially destructive event or over a significant period of time.
-
E.
hasSurvivors
Indicates that one or more entities continue to exist or remain alive after a particular event, condition, or incident.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0caa0988190872fc7648e64571f |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:11 p.m.