Triple
T3035098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | transcontinental telegraph |
E82988
|
entity |
| Predicate | communicationLatency |
P45126
|
FINISHED |
| Object | near-instant compared to mail |
—
|
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: near-instant compared to mail | Statement: [transcontinental telegraph, communicationLatency, near-instant compared to mail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationLatency Context triple: [transcontinental telegraph, communicationLatency, near-instant compared to mail]
-
A.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
B.
communicationCapability
Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
-
C.
communicationStatus
Indicates the current state or condition of a communication process or exchange between entities (e.g., pending, active, failed, completed).
-
D.
hasCommunicationFrequency
Indicates how often communication occurs between the related entities.
-
E.
communicationModel
Indicates the type or framework of communication used or assumed in the relationship between entities.
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b2a40b48190bfa7cdbb0fbd87f8 |
completed | March 8, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 3:01 p.m.