Triple
T2947854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACM SIGMETRICS Test of Time Award |
E79544
|
entity |
| Predicate | fieldOverlap |
P11740
|
FINISHED |
| Object | computer networks performance |
—
|
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: computer networks performance | Statement: [ACM SIGMETRICS Test of Time Award, fieldOverlap, computer networks performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOverlap Context triple: [ACM SIGMETRICS Test of Time Award, fieldOverlap, computer networks performance]
-
A.
fieldIntersection
chosen
Indicates that two or more fields or domains share a common overlapping area or set of elements.
-
B.
fieldCovered
Indicates that a specified field or area is physically or functionally covered by some material, object, or condition.
-
C.
overlapsWith
Indicates that two entities share a common part or region in space, time, or extent, but neither is completely contained within the other.
-
D.
coversField
Indicates that one entity extends over, protects, or occupies the surface or area of a field associated with another entity.
-
E.
presentDayAdministrativeAreaOverlap
Indicates that two entities share a common geographic area within their current official administrative boundaries.
- 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98b5916c8190b1163bf0b7fa136a |
completed | March 8, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.