Triple
T17517732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tranquility |
E426607
|
entity |
| Predicate | peakConcurrentUsersRecord |
P34607
|
FINISHED |
| Object | over 60,000 concurrent players |
—
|
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: over 60,000 concurrent players | Statement: [Tranquility, peakConcurrentUsersRecord, over 60,000 concurrent players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakConcurrentUsersRecord Context triple: [Tranquility, peakConcurrentUsersRecord, over 60,000 concurrent players]
-
A.
peakDayAttendance
Indicates the number of attendees present on the single highest-attendance day within a given period or event.
-
B.
peakUse
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
-
C.
approximateUserPeak
Indicates that one value or event is an estimated or inferred maximum point associated with a particular user.
-
D.
deploymentPeakNumber
Indicates the maximum number of deployments (or deployment instances) reached during a specified period or under given conditions.
-
E.
usagePeak
chosen
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452615a8481909974e9855ea7a8e4 |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.