Triple
T9187806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARexx |
E220501
|
entity |
| Predicate | typicalExtension |
P82558
|
FINISHED |
| Object | .rexx |
—
|
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: .rexx | Statement: [ARexx, typicalExtension, .rexx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalExtension Context triple: [ARexx, typicalExtension, .rexx]
-
A.
typicalMIMEType
Indicates the standard or most commonly used MIME (media) type associated with a given resource or format.
-
B.
formerExtension
Indicates that one entity previously served as an extension or subsidiary part of another entity, but no longer holds that status.
-
C.
extension
Indicates that one entity is a lengthening, continuation, or added part of another entity beyond its original limits.
-
D.
containerFilenameExtension
chosen
Indicates that one item is a filename extension associated with a particular container format.
-
E.
definesExtension
Indicates that one entity specifies or establishes the extension, scope, or detailed form of another 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc31bd6f88190b2ea644420995e41 |
completed | April 1, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:24 p.m.