Triple
T33029510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Relay |
E845124
|
entity |
| Predicate | relationToInternetHistory |
—
|
GENERATED |
| Object | early online communication service |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToInternetHistory Context triple: [Relay, relationToInternetHistory, early online communication service]
-
A.
relationToUTMB
Indicates a relationship or association that an entity has with UTMB (e.g., affiliation, connection, or relevance to UTMB).
-
B.
historicalRelationsWith
Indicates a relationship where one entity has documented or recognized connections, interactions, or associations with another entity in the past.
-
C.
historicallyLinked
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
D.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
-
E.
recentHistory
Indicates that one entity represents the most recent sequence of events, states, or interactions associated with another entity.
- F. None of above. chosen
Provenance (1 batch)
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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:24 a.m.