Triple
T34357068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laura Holt |
E881759
|
entity |
| Predicate | networkRun |
P180582
|
FINISHED |
| Object | 1982–1987 on NBC |
—
|
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: 1982–1987 on NBC | Statement: [Laura Holt, networkRun, 1982–1987 on NBC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkRun Context triple: [Laura Holt, networkRun, 1982–1987 on NBC]
-
A.
networkSuite
Indicates that an entity is part of, provided by, or associated with a particular network-related software or service suite.
-
B.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
C.
netWork
Indicates a relationship where entities are connected or interact within a shared system, structure, or set of links that enables communication or exchange.
-
D.
originalNetworkRunStart
Indicates the time or event at which a network process, operation, or run was first initiated.
-
E.
networkIntended
Indicates that one entity is designed or purposed to be used within, connected to, or operate over a particular network or networking context.
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: May 1, 2026, 1:58 a.m.