Triple
T8040996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Bridge (Civil War-era structure) |
E187437
|
entity |
| Predicate | heavilyUsedBy |
P24441
|
FINISHED |
| Object | Union military |
—
|
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: Union military | Statement: [Long Bridge (Civil War-era structure), heavilyUsedBy, Union military]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heavilyUsedBy Context triple: [Long Bridge (Civil War-era structure), heavilyUsedBy, Union military]
-
A.
isFamouslyUsedBy
Indicates that something is widely and notably used by a particular person, group, or entity, in a way that is broadly recognized or associated with them.
-
B.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
-
C.
laterUsedBy
Indicates that something is subsequently utilized or employed by a specified entity at a later time.
-
D.
alsoUsedBy
Indicates that something is additionally utilized or employed by another entity, beyond any primary or previously mentioned user.
-
E.
wasUsedBy
chosen
Indicates that something served as a tool, resource, or means for an agent to perform an action or achieve a result.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f1d62c48190bf4a6cd17517c5dc |
completed | March 31, 2026, 3:27 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:23 p.m.