Triple
T7421190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotus SmartSuite |
E171248
|
entity |
| Predicate | supportedFileFormat |
P8463
|
FINISHED |
| Object | .123 |
—
|
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: .123 | Statement: [Lotus SmartSuite, supportedFileFormat, .123]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedFileFormat Context triple: [Lotus SmartSuite, supportedFileFormat, .123]
-
A.
hasFileFormat
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
B.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
C.
canImportFormat
chosen
Indicates that an entity has the capability to import or read data in a specified format.
-
D.
supportsCompressedFiles
Indicates that one entity is capable of handling, reading, or working with files that are stored in a compressed format.
-
E.
typicalPictureFormat
Indicates the standard or most commonly used picture format associated with an entity (such as a device, medium, or context).
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2ebc520819087cfc2eb9dda0e17 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.