Triple
T37932802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QXD |
E946261
|
entity |
| Predicate | mayBeConvertedTo |
P631
|
FINISHED |
| Object |
—
|
NE NERFINISHED |
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: PDF | Statement: [QXD, mayBeConvertedTo, PDF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeConvertedTo Context triple: [QXD, mayBeConvertedTo, PDF]
-
A.
convertsTo
chosen
Indicates that one entity is transformed or changed into another entity, typically resulting in a different state, form, or representation.
-
B.
allowsConversionTo
Indicates that one entity permits or enables transformation or change into another specified form or state.
-
C.
isConversion
Indicates that one entity is transformed or converted into another, typically changing its form, type, or representation.
-
D.
mayBeTranslatedTo
Indicates that one entity can potentially be converted or rendered into another entity in a different language or representation through translation.
-
E.
mayBeAdaptedTo
Indicates that something has the potential or suitability to be modified or adjusted for use in a different context, condition, or purpose.
- 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_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:20 p.m.