Triple
T28052367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adams Express Company |
E708860
|
entity |
| Predicate | expandedVia |
P5633
|
FINISHED |
| Object | acquisitions of smaller express firms |
—
|
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: acquisitions of smaller express firms | Statement: [Adams Express Company, expandedVia, acquisitions of smaller express firms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedVia Context triple: [Adams Express Company, expandedVia, acquisitions of smaller express firms]
-
A.
expandedBy
chosen
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
B.
expandedAs
Indicates that one entity is a more detailed, elaborated, or fully written-out form of another, capturing how the latter is expanded from the former.
-
C.
expandedAfter
Indicates that one entity increases in size, scope, or extent after another specified event or point in time.
-
D.
expandedDuring
Indicates that an entity increased in size, scope, or extent over the course of a specified time period or event.
-
E.
expandedAcross
Indicates that something has grown or extended so that it now spans or covers multiple areas, regions, or segments.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 8:34 p.m.