Triple
T25321860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compatible Time-Sharing System |
E634903
|
entity |
| Predicate | supportedUsersSimultaneously |
P31535
|
FINISHED |
| Object | dozens of users |
—
|
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: dozens of users | Statement: [Compatible Time-Sharing System, supportedUsersSimultaneously, dozens of users]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedUsersSimultaneously Context triple: [Compatible Time-Sharing System, supportedUsersSimultaneously, dozens of users]
-
A.
supportsAPStationConcurrent
Indicates that a device or system can support an access point (AP) station operating concurrently with other modes or connections.
-
B.
supportsMultiuser
chosen
Indicates that the subject is capable of handling or enabling simultaneous use by multiple users.
-
C.
supportsDeviceCount
Indicates the number of devices that a system, service, or component is capable of supporting concurrently.
-
D.
userCount
Indicates the number of users associated with or involved in a given context or entity.
-
E.
cannotHoldSimultaneously
Indicates that two conditions or states are mutually exclusive and cannot both be true or occur at the same time.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 21, 2026, 1:28 p.m.