Triple
T7253377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chronica |
E157657
|
entity |
| Predicate | workLostStatus |
P32274
|
FINISHED |
| Object | largely lost |
—
|
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: largely lost | Statement: [Chronica, workLostStatus, largely lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workLostStatus Context triple: [Chronica, workLostStatus, largely lost]
-
A.
lostStatus
Indicates that an entity has transitioned into a state of being lost, missing, or no longer in its expected or intended possession or location.
-
B.
worksStatus
Indicates the current state or condition of an entity’s work or project, such as whether it is planned, in progress, completed, or otherwise categorized.
-
C.
loserStatus
Indicates that an entity has been judged or designated as the loser in a particular comparison, contest, or evaluative context.
-
D.
hasLostWorks
chosen
Indicates that an entity has created works that are no longer extant, missing, or have not survived.
-
E.
workPreservationStatus
Indicates the current state or condition of efforts to preserve a particular work (such as whether it is preserved, partially preserved, or lost).
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea9d41908190bb76c6a5b9d5b1a2 |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:56 p.m.