Triple
T2889539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XEmacs |
E59584
|
entity |
| Predicate | customizationMethod |
P33710
|
FINISHED |
| Object | Emacs Lisp configuration files |
—
|
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: Emacs Lisp configuration files | Statement: [XEmacs, customizationMethod, Emacs Lisp configuration files]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customizationMethod Context triple: [XEmacs, customizationMethod, Emacs Lisp configuration files]
-
A.
customizableBy
chosen
Indicates that one entity can be modified, configured, or tailored in some way by another entity.
-
B.
custom
Indicates that something is specially created, configured, or tailored for a particular purpose, context, or user rather than being standard or generic.
-
C.
veilCustom
Indicates a customary or traditional practice involving the wearing or use of a veil.
-
D.
socialCustom
Indicates a culturally shared, customary way of behaving or interacting that is expected or considered appropriate within a particular social group or context.
-
E.
adjustmentType
Indicates the specific kind or category of modification applied to an existing value, state, or configuration within the relationship.
- 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abe04a68ac8190aaeafe52138beb74 |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd17bcdc8190aa47274a50ba4ad4 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:04 p.m.