Triple
T9897410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | File History |
E182210
|
entity |
| Predicate | backsUp |
P91045
|
FINISHED |
| Object | libraries |
—
|
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: libraries | Statement: [File History, backsUp, libraries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backsUp Context triple: [File History, backsUp, libraries]
-
A.
backing
Indicates providing support, endorsement, or financial/resources assistance to someone or something, often enabling or strengthening their actions or position.
-
B.
backType
Indicates the type or category of a backing or support associated with an entity.
-
C.
backedFor
Indicates that one entity provides support, endorsement, or backing for another entity, often in a financial, political, or strategic context.
-
D.
backSupport
Indicates that one entity provides physical or structural support to the back of another entity.
-
E.
broughtBack
Indicates that an entity caused another entity to return to a previous place, state, or condition.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4ab15f881909f75a8e01051dbc4 |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:40 p.m.