Triple
T12515387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ninja build system |
E299179
|
entity |
| Predicate | inputFileFormat |
P90391
|
FINISHED |
| Object | .ninja 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: .ninja files | Statement: [Ninja build system, inputFileFormat, .ninja files]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputFileFormat Context triple: [Ninja build system, inputFileFormat, .ninja files]
-
A.
fileFormatStandard
Indicates that something conforms to, specifies, or defines a standardized structure and rules for how data is organized and stored in a file.
-
B.
primaryInputFormat
chosen
Indicates the data format that is expected or used as the main input for a given process, system, or operation.
-
C.
storageFormat
Indicates the specific way in which data or content is physically or logically organized, encoded, and stored.
-
D.
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.
-
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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.