Triple
T36622438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swan Hunter |
E904077
|
entity |
| Predicate | afterMergerName |
P71745
|
FINISHED |
| Object | Swan Hunter & Wigham Richardson |
—
|
NE NERFINISHED |
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: Swan Hunter & Wigham Richardson | Statement: [Swan Hunter, afterMergerName, Swan Hunter & Wigham Richardson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterMergerName Context triple: [Swan Hunter, afterMergerName, Swan Hunter & Wigham Richardson]
-
A.
laterMergedWith
Indicates that one entity was combined into and became part of another entity at a subsequent point in time.
-
B.
afterAcquisitionName
chosen
Indicates that the object entity represents the name used by a company or organization after it has been acquired.
-
C.
behaviorAfterMerge
Indicates the resulting behavior or state of an entity or system after two or more components have been merged.
-
D.
missionAfterMerge
Indicates that one mission occurs or is valid only after another mission has been merged or combined into it.
-
E.
precededByMerger
Indicates that one entity existed or occurred before another as a result of a merger that led to the latter entity.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.