Triple
T35281335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorymoog |
E1018940
|
entity |
| Predicate | hasUnisonMode |
P193021
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Memorymoog, hasUnisonMode, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnisonMode Context triple: [Memorymoog, hasUnisonMode, yes]
-
A.
isUnifiedSystem
Indicates that multiple components or elements function together as a single, coherent, integrated system.
-
B.
hasCoopMode
Indicates that something supports or includes a cooperative mode of operation or gameplay involving multiple participants working together.
-
C.
hasUnifiedCommand
Indicates that multiple entities operate under a single, centralized authority or leadership structure for coordinated control.
-
D.
hasUnitFeature
Indicates that something possesses a specific unit-related characteristic or attribute, such as a measurable feature expressed in defined units.
-
E.
hasIntegratedUnit
Indicates that one entity includes another entity as a built-in or internally combined component or unit.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
| PDg | Predicate description generation | batch_69fd35d029588190a525aa8a506e7708 |
completed | May 8, 2026, 1:01 a.m. |
Created at: May 3, 2026, 4:03 p.m.