Triple
T37932741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QXP |
E946260
|
entity |
| Predicate | fileCategory |
P159120
|
FINISHED |
| Object | page layout file |
—
|
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: page layout file | Statement: [QXP, fileCategory, page layout file]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fileCategory Context triple: [QXP, fileCategory, page layout file]
-
A.
fileTypeFamily
chosen
Indicates that one file type belongs to, or is categorized under, a broader family or group of related file types.
-
B.
fileTypeCode
Indicates the specific classification or category code that identifies the type or format of a file.
-
C.
functionCategory
Indicates that one function is classified as belonging to a particular functional category or type.
-
D.
filenameType
Indicates the type or category associated with a given filename (e.g., file format, role, or classification).
-
E.
typicalFileType
Indicates that one entity is the usual or commonly associated file type for the other entity.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.