Triple
T10020183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MapMessage |
E200592
|
entity |
| Predicate | valueAccessPattern |
P79849
|
FINISHED |
| Object | key-based access |
—
|
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: key-based access | Statement: [MapMessage, valueAccessPattern, key-based access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueAccessPattern Context triple: [MapMessage, valueAccessPattern, key-based access]
-
A.
accessPattern
chosen
Indicates how an entity interacts with or retrieves data or resources, such as the manner, frequency, or sequence of access.
-
B.
valueAt
Indicates that one entity specifies the value or content associated with another entity at a particular point, position, or context.
-
C.
value
Indicates that one entity possesses, represents, or corresponds to a particular quantity, quality, or assigned worth.
-
D.
valueExpressed
Indicates that a particular value, opinion, or quantitative measure is articulated, represented, or made explicit by an entity or expression.
-
E.
accessPath
Indicates a path, route, or means by which something can be reached, entered, or accessed.
- 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd777b208190ad75eac79eec0c2f |
completed | April 2, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:53 p.m.