Triple
T18528812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TinyMCE |
E452784
|
entity |
| Predicate | developer |
P73
|
FINISHED |
| Object |
Ephox
Ephox is a software company best known for providing rich text editing and content creation technologies, including contributions to the TinyMCE editor.
|
E1328954
|
NE FINISHED |
How this triple was built (4 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: Ephox | Statement: [TinyMCE, developer, Ephox]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ephox Context triple: [TinyMCE, developer, Ephox]
-
A.
Phenax
Phenax is a small genus of flowering plants in the hemp family Cannabaceae, native to the Americas and typically found in tropical to subtropical regions.
-
B.
Epher
Epher is a minor biblical figure traditionally regarded as a descendant of Abraham through Keturah and Midian.
-
C.
Erixx
Erixx is a regional railway company in Germany that operates local passenger train services in Lower Saxony and surrounding areas.
-
D.
Fenix
Fenix is a legendary Protoss warrior from the StarCraft universe, renowned for his bravery, loyalty, and pivotal role in key battles alongside heroes like Tassadar and Jim Raynor.
-
E.
Epifan
Epifan is a historic Russian town that once served as the administrative center of Epifansky Uyezd in the Tula Governorate.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Ephox Triple: [TinyMCE, developer, Ephox]
Generated description
Ephox is a software company best known for providing rich text editing and content creation technologies, including contributions to the TinyMCE editor.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Ephox Target entity description: Ephox is a software company best known for providing rich text editing and content creation technologies, including contributions to the TinyMCE editor.
-
A.
Phenax
Phenax is a small genus of flowering plants in the hemp family Cannabaceae, native to the Americas and typically found in tropical to subtropical regions.
-
B.
Epher
Epher is a minor biblical figure traditionally regarded as a descendant of Abraham through Keturah and Midian.
-
C.
Erixx
Erixx is a regional railway company in Germany that operates local passenger train services in Lower Saxony and surrounding areas.
-
D.
Fenix
Fenix is a legendary Protoss warrior from the StarCraft universe, renowned for his bravery, loyalty, and pivotal role in key battles alongside heroes like Tassadar and Jim Raynor.
-
E.
Epifan
Epifan is a historic Russian town that once served as the administrative center of Epifansky Uyezd in the Tula Governorate.
- F. None of above. chosen
Provenance (5 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e533fad2d081908395914d6a6b4eb1 |
completed | April 19, 2026, 7:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a049178ea1c819085480137adfb3841 |
completed | May 13, 2026, 2:58 p.m. |
| NEDg | Description generation | batch_6a04921b1a508190b8bb6d6c4597ab99 |
completed | May 13, 2026, 3 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0492ba4ea08190b59510b221ad5d21 |
completed | May 13, 2026, 3:03 p.m. |
Created at: April 10, 2026, 11:37 a.m.