Triple
T16907659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ctangle |
E424603
|
entity |
| Predicate | typicalFileExtensionInput |
P107865
|
FINISHED |
| Object | .w |
—
|
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: .w | Statement: [ctangle, typicalFileExtensionInput, .w]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFileExtensionInput Context triple: [ctangle, typicalFileExtensionInput, .w]
-
A.
typicalFileFormat
Indicates the usual or standard file format typically associated with or used for a given entity or context.
-
B.
typicalFileType
chosen
Indicates that one entity is the usual or commonly associated file type for the other entity.
-
C.
filenameType
Indicates the type or category associated with a given filename (e.g., file format, role, or classification).
-
D.
includesExtension
Indicates that one entity contains or incorporates another entity as an added or supplementary extension.
-
E.
fileTypeCode
Indicates the specific classification or category code that identifies the type or format of a file.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3ca39f9b08190b15106c6caf895ec |
completed | April 18, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.