Triple
T34955449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MicroEMACS |
E1008111
|
entity |
| Predicate | hasNotableFork |
P48596
|
FINISHED |
| Object | JASSPA MicroEmacs |
E1008111
|
NE 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: JASSPA MicroEmacs | Statement: [MicroEMACS, hasNotableFork, JASSPA MicroEmacs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFork Context triple: [MicroEMACS, hasNotableFork, JASSPA MicroEmacs]
-
A.
notableFork
chosen
Indicates that one entity is a significant fork or derivative version of another, typically diverging in a notable or influential way from the original.
-
B.
notableBranch
Indicates that one entity is a particularly significant or prominent subdivision, offshoot, or branch of another entity.
-
C.
hasNotableVersion
Indicates that an entity has a specific version or variant that is particularly significant, distinguished, or noteworthy compared to other versions.
-
D.
hasNotableParent
Indicates that an entity has a parent who is distinguished, prominent, or otherwise notable.
-
E.
hasNotableIssue
Indicates that an entity is associated with a significant problem, concern, or defect that is noteworthy or exceptional compared to typical cases.
- F. None of above.
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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a03544239d4819087b6c232d6804977 |
completed | May 12, 2026, 4:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37a8ce4e0881909578bc67acb0ef51 |
completed | June 21, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0353d685688190b01df77fc2f62bf2 |
completed | May 12, 2026, 4:22 p.m. |
Created at: May 3, 2026, 4 p.m.