Triple
T37932888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft 365 Family |
E946263
|
entity |
| Predicate | maximumNumberOfUsers |
P194974
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [Microsoft 365 Family, maximumNumberOfUsers, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumNumberOfUsers Context triple: [Microsoft 365 Family, maximumNumberOfUsers, 6]
-
A.
maximumUsage
Indicates the highest allowable or observed amount, frequency, or extent to which something can be used within a defined context or period.
-
B.
maximumPlayerCount
Indicates the largest number of players that can participate at the same time in the related context or activity.
-
C.
maximumNumberOfSeats
Indicates the greatest allowable or physically available number of seats associated with an entity or context.
-
D.
playerLimit
Indicates the maximum number of players allowed to participate in a given game, session, or activity.
-
E.
maxNumberOfValues
Indicates the maximum count of distinct values that may be associated with a given entity or property in this relationship.
- F. None of above. chosen
Provenance (4 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
| PDg | Predicate description generation | batch_69fd91a44268819081b372296e3aa116 |
completed | May 8, 2026, 7:32 a.m. |
Created at: May 3, 2026, 4:20 p.m.