Triple
T8413352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human68k |
E198673
|
entity |
| Predicate | supportsExecutableFormat |
P8463
|
FINISHED |
| Object | X68000 binary format |
—
|
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: X68000 binary format | Statement: [Human68k, supportsExecutableFormat, X68000 binary format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsExecutableFormat Context triple: [Human68k, supportsExecutableFormat, X68000 binary format]
-
A.
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.
-
B.
hasWorkingFormat
Indicates that one entity possesses or is associated with a functional or operational format of another entity.
-
C.
canExportToFormat
Indicates that something has the capability to be exported or converted into a specified file or data format.
-
D.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
E.
canImportFormat
chosen
Indicates that an entity has the capability to import or read data in a specified format.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83e18e7c8190a30b14136dee3d93 |
completed | March 31, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.