Triple
T9945830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAT table |
E195200
|
entity |
| Predicate | oftenDuplicatedAs |
P76200
|
FINISHED |
| Object | backup FAT table |
—
|
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: backup FAT table | Statement: [FAT table, oftenDuplicatedAs, backup FAT table]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenDuplicatedAs Context triple: [FAT table, oftenDuplicatedAs, backup FAT table]
-
A.
duplicates
chosen
Indicates that one entity is an exact or near-exact copy of another entity in content, structure, or function.
-
B.
repetitionOf
Indicates that one entity is a repeated occurrence or instance of another entity, preserving the same content or pattern.
-
C.
oftenAccompaniedBy
Indicates that one entity is frequently found together with, occurs alongside, or is commonly associated in presence or use with another entity.
-
D.
causesRepetitionOf
Indicates that one entity brings about or is responsible for the recurrence or repeated occurrence of another entity or event.
-
E.
oftenReplacedBy
Indicates that one entity is frequently substituted or superseded by another in similar contexts or uses.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb655fba0819084a1e757b68c25d4 |
completed | April 2, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.