Triple
T4442490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mruby |
E96204
|
entity |
| Predicate | extensionSystem |
P11253
|
FINISHED |
| Object | mrbgems |
—
|
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: mrbgems | Statement: [mruby, extensionSystem, mrbgems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extensionSystem Context triple: [mruby, extensionSystem, mrbgems]
-
A.
extensionMechanism
chosen
Indicates that one entity provides a way to extend, customize, or add new functionality or components to another entity.
-
B.
extension
Indicates that one entity is a lengthening, continuation, or added part of another entity beyond its original limits.
-
C.
extensionOpened
Indicates that a software extension has been activated or launched from its previously closed or inactive state.
-
D.
extendedOn
Indicates that one entity continues, prolongs, or expands the duration, scope, or effect of another entity beyond its original limit.
-
E.
extendedBy
Indicates that one entity builds upon, enlarges, or adds to the scope, functionality, or duration of another entity.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355aef21c819088f168a23f1933a6 |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.