Triple
T26347910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotus |
E662823
|
entity |
| Predicate | spreadsheetFeatures |
P9789
|
FINISHED |
| Object | graphing |
—
|
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: graphing | Statement: [Lotus, spreadsheetFeatures, graphing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spreadsheetFeatures Context triple: [Lotus, spreadsheetFeatures, graphing]
-
A.
hasSpreadsheet
Indicates that one entity possesses, is associated with, or contains a spreadsheet resource.
-
B.
officeIncludes
Indicates that an office contains, encompasses, or has within its scope a specified subordinate space, role, or resource.
-
C.
supportsOffice
Indicates that one entity provides assistance, resources, or endorsement to an office or officeholder in performing its functions or maintaining its operations.
-
D.
hasOfficeComponent
Indicates that something includes, contains, or is composed of an office-related part or element.
-
E.
formsFeature
chosen
Indicates that one entity constitutes or creates a characteristic, component, or distinguishing element of 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fa904a08190938352e5413c1e77 |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:43 p.m.