Triple
T31992416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MATE core applications |
E816906
|
entity |
| Predicate | includesFunctionality |
P40816
|
FINISHED |
| Object | file management |
—
|
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: file management | Statement: [MATE core applications, includesFunctionality, file management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFunctionality Context triple: [MATE core applications, includesFunctionality, file management]
-
A.
providesFunctionalityOf
chosen
Indicates that one entity supplies, implements, or makes available the capabilities or functions that are normally associated with another entity.
-
B.
hasFacilityFunction
Indicates that a facility performs, supports, or is designated for a particular function or operational role.
-
C.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
D.
definesFunctioningOf
Indicates that one entity specifies or determines how another entity operates or functions.
-
E.
isFeatureRich
Indicates that an entity possesses a large number and wide variety of capabilities or functionalities.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01a23d8b148190ac2c8765aa9227c4 |
completed | May 11, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_6a01a1e8bb90819096647e929bfb3db8 |
completed | May 11, 2026, 9:31 a.m. |
Created at: May 1, 2026, 12:13 a.m.