Triple
T7894758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xenix |
E183317
|
entity |
| Predicate | concurrentUsers |
P22398
|
FINISHED |
| Object | multiple terminals |
—
|
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: multiple terminals | Statement: [Xenix, concurrentUsers, multiple terminals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concurrentUsers Context triple: [Xenix, concurrentUsers, multiple terminals]
-
A.
userCount
chosen
Indicates the number of users associated with or involved in a given context or entity.
-
B.
circulationUsers
Indicates a relationship where users are involved in or affected by the circulation or lending of items within a system.
-
C.
maxOnlinePlayers
Indicates the maximum number of players that can be connected or participating simultaneously in an online context.
-
D.
sessionCount
Indicates the number of distinct sessions associated with an entity or interaction context.
-
E.
estimatedMemberCount
Indicates the approximate or predicted number of members associated with an entity.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a15a7e88190a05474844817e5d2 |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:01 p.m.