Triple
T33027726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NLST |
E845086
|
entity |
| Predicate | differenceFrom LIST |
P74132
|
FINISHED |
| Object | NLST omits file attributes and formatting |
—
|
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: NLST omits file attributes and formatting | Statement: [NLST, differenceFrom LIST, NLST omits file attributes and formatting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differenceFrom LIST Context triple: [NLST, differenceFrom LIST, NLST omits file attributes and formatting]
-
A.
differenceFromStates
Indicates that one state or condition is distinct from, or deviates in some way from, another state or condition.
-
B.
differenceDescription
chosen
Indicates a textual explanation that characterizes how two entities differ from each other.
-
C.
isDifferenceOf
Indicates that one quantity or entity represents the result obtained by subtracting one specified quantity or entity from another.
-
D.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
E.
differenceFromSQL
Indicates that something differs in behavior, structure, or result from its equivalent in standard SQL.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:23 a.m.