Triple
T31646523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poly/ML |
E807596
|
entity |
| Predicate | hasInteractiveREPL |
P79901
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Poly/ML, hasInteractiveREPL, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteractiveREPL Context triple: [Poly/ML, hasInteractiveREPL, true]
-
A.
supportsInteractiveWidgets
Indicates that an entity is capable of handling or enabling interactive widgets within its context or environment.
-
B.
supportsInteractiveMenus
Indicates that an entity provides or is compatible with interactive, menu-based user interfaces or options.
-
C.
hasCommandLineInterface
chosen
Indicates that an entity provides or supports interaction through a command-line interface (CLI).
-
D.
hasInteractiveActivity
Indicates that an entity includes or is associated with an activity that requires active user participation or engagement.
-
E.
hasInteractionMode
Indicates the way in which two entities engage or interact with each other, specifying the manner, channel, or pattern of their interaction.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
Created at: April 30, 2026, 10:51 p.m.