Triple
T10144012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UR-100 |
E231655
|
entity |
| Predicate | deploymentPeakPeriod |
P70162
|
FINISHED |
| Object | early 1970s |
—
|
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 1970s | Statement: [UR-100, deploymentPeakPeriod, early 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentPeakPeriod Context triple: [UR-100, deploymentPeakPeriod, early 1970s]
-
A.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
B.
operationalPeak
Indicates the highest level or period of performance, capacity, or activity that a system, process, or entity reaches during its operation.
-
C.
activityPeakPeriod
chosen
Indicates the time period during which an activity reaches its highest level or intensity.
-
D.
leaderDuringPeak
Indicates that an entity served as the primary leader of another entity during the latter’s peak or most successful period.
-
E.
peakServicePeriod
Indicates the time interval during which a service experiences its highest or most intensive level of use or operation.
- 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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdeb28a1708190b46499dbe51a694a |
completed | April 2, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:07 p.m.