Triple
T7980928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WS-* specifications |
E185566
|
entity |
| Predicate | historicalPeakUsage |
P4936
|
FINISHED |
| Object | early 2000s to late 2000s |
—
|
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: early 2000s to late 2000s | Statement: [WS-* specifications, historicalPeakUsage, early 2000s to late 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeakUsage Context triple: [WS-* specifications, historicalPeakUsage, early 2000s to late 2000s]
-
A.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
-
B.
historicalPeak
chosen
Indicates that the related value or state represents the highest level ever reached by something within a historical or recorded time frame.
-
C.
highestPeakAccessed
Indicates that one entity has reached or visited the tallest peak associated with another entity or within a specified context.
-
D.
operationalPeak
Indicates the highest level or period of performance, capacity, or activity that a system, process, or entity reaches during its operation.
-
E.
peakUse
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c274ce48190854d389d43ce14b8 |
completed | March 31, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:15 p.m.