Triple
T8952449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola 6800 |
E213385
|
entity |
| Predicate | stackLocation |
P85847
|
FINISHED |
| Object | user-definable in memory |
—
|
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: user-definable in memory | Statement: [Motorola 6800, stackLocation, user-definable in memory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stackLocation Context triple: [Motorola 6800, stackLocation, user-definable in memory]
-
A.
frameLocation
Indicates that one entity serves as the spatial or contextual frame of reference within which another entity is located or interpreted.
-
B.
trapLocation
Indicates the specific place or area where a trap is set, located, or expected to be found.
-
C.
reentryLocation
Indicates the place or area where an entity returns or re-enters after having left or exited a previous location or state.
-
D.
hasStackPointer
Indicates that an entity maintains or uses a specific stack pointer reference within a stack-based memory or execution context.
-
E.
slotLocation
Indicates the specific position or compartment within a larger container or system where an item is placed or assigned.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc670dc0c88190b1f59e96ad88e4ee |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 6:59 p.m.