Triple
T33027757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NLST |
E845086
|
entity |
| Predicate | isMinimalVariantOf |
P118797
|
FINISHED |
| Object | LIST directory listing |
—
|
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: LIST directory listing | Statement: [NLST, isMinimalVariantOf, LIST directory listing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMinimalVariantOf Context triple: [NLST, isMinimalVariantOf, LIST directory listing]
-
A.
isShortenedVariantOf
chosen
Indicates that one form of an expression is a shortened or abbreviated version of another, longer form.
-
B.
isRobustVariantOf
Indicates that one entity is a strengthened, more resilient, or more general form of another, preserving the original’s core properties while improving its robustness.
-
C.
isNumberedVariantOf
Indicates that one entity is a specific numbered version or edition of another, more general entity.
-
D.
denotesVariantOf
Indicates that one entity is a variant or alternative form of another, typically sharing core identity or function with some differences.
-
E.
isVersionOf
Indicates that one entity is a particular version, edition, or variant derived from another entity.
- 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_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:23 a.m.