Triple
T2113902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plink |
E42563
|
entity |
| Predicate | interactiveMode |
P23418
|
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: [Plink, interactiveMode, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactiveMode Context triple: [Plink, interactiveMode, yes]
-
A.
instrumentMode
Indicates the manner, setting, or operational mode in which an instrument is used to perform an action or measurement.
-
B.
userInteractionModel
chosen
Indicates how a user is expected to interact with a system, defining the style, rules, or pattern of those interactions.
-
C.
displayMode
Indicates how content or information is visually presented or arranged to the user.
-
D.
interactionPoint
Indicates a specific location or moment where two or more entities come into contact or engage with each other.
-
E.
userInterface
Indicates a relationship where one entity serves as the interface or interaction layer through which a user engages with another system, service, or resource.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb05b51c81908a78c816f492c45c |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.