Triple
T6469976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East_Asian_Width |
E142322
|
entity |
| Predicate | hasDataFile |
P70988
|
FINISHED |
| Object | EastAsianWidth.txt |
—
|
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: EastAsianWidth.txt | Statement: [East_Asian_Width, hasDataFile, EastAsianWidth.txt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDataFile Context triple: [East_Asian_Width, hasDataFile, EastAsianWidth.txt]
-
A.
hasDataFields
Indicates that an entity possesses or is associated with specific data fields or attributes.
-
B.
hasConfigurationFile
Indicates that an entity is associated with or defined by a specific configuration file.
-
C.
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.
-
D.
hasFileExtension
Indicates that one entity (typically a file) possesses a specific file extension denoting its type or format.
-
E.
hasMetadata
Indicates that one entity is associated with descriptive or informational data about another entity.
- F. None of above. chosen
Provenance (4 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a2e896481908ed004e3b0a33121 |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c067da970481908a038995ba7dfb4b |
completed | March 22, 2026, 10:06 p.m. |
Created at: March 22, 2026, 4:50 p.m.