Triple
T8608992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GDM |
E203872
|
entity |
| Predicate | configurationFileFormat |
P80623
|
FINISHED |
| Object | text configuration files |
—
|
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: text configuration files | Statement: [GDM, configurationFileFormat, text configuration files]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationFileFormat Context triple: [GDM, configurationFileFormat, text configuration files]
-
A.
configFileFormat
chosen
Indicates the file format or syntax standard used by a configuration file.
-
B.
configurationFileExtension
Indicates the file extension used for a configuration file associated with an entity.
-
C.
defaultPackageFormat
Indicates the standard or primary packaging format that is used by default for an item or distribution.
-
D.
configurationName
Indicates the specific label or identifier assigned to a particular configuration setting or setup.
-
E.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46ed77588190a872d22d9d1f7429 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.