Triple
T34955449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MicroEMACS |
E1008111
|
entity |
| Predicate | hasNotableFork |
—
|
GENERATED |
| Object | JASSPA MicroEmacs |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
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 (1 batch)
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. |
Created at: May 3, 2026, 4 p.m.