Triple
T29606719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yet Another Markup Language |
E754594
|
entity |
| Predicate | commonlyEditedWith |
P193357
|
FINISHED |
| Object | text editors |
—
|
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: text editors | Statement: [Yet Another Markup Language, commonlyEditedWith, text editors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyEditedWith Context triple: [Yet Another Markup Language, commonlyEditedWith, text editors]
-
A.
coEditor
Indicates that two or more entities share responsibility for editing the same work or publication.
-
B.
editedIn
Indicates that an entity was modified, revised, or otherwise altered within a particular context, tool, environment, or time frame.
-
C.
co-editedWith
Indicates that two or more entities jointly served as editors of the same work or publication.
-
D.
editedTo
Indicates that one entity has been modified, revised, or altered in order to become the other entity.
-
E.
editingContributesTo
Indicates that the act of editing one entity plays a role in producing, improving, or influencing another entity.
- F. None of above. chosen
Provenance (4 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69fd4445f8c08190bb2dc27e0971c55d |
completed | May 8, 2026, 2:02 a.m. |
Created at: April 28, 2026, 6:25 p.m.