Triple
T34441968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jardine, Matheson & Co. |
E884120
|
entity |
| Predicate | hasMajorBusinessInterest |
P16009
|
FINISHED |
| Object | shipping |
—
|
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: shipping | Statement: [Jardine, Matheson & Co., hasMajorBusinessInterest, shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorBusinessInterest Context triple: [Jardine, Matheson & Co., hasMajorBusinessInterest, shipping]
-
A.
hasEconomicInterest
Indicates that one entity stands to gain or lose financially or materially from the performance, decisions, or outcomes associated with another entity.
-
B.
hasMajorBusinessLine
chosen
Indicates that an entity conducts a primary or significant line of business in a specified area, sector, or activity.
-
C.
hasMajorEmployerType
Indicates the type or category of major employer associated with an entity.
-
D.
hasMajorEmployer
Indicates that an entity has a primary or most significant employer with which it is chiefly affiliated for work or occupation.
-
E.
hasManagementInterest
Indicates that one entity holds a managerial, controlling, or oversight interest in another entity or asset.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a01a819644c819094c58d083d525da0 |
completed | May 11, 2026, 9:57 a.m. |
| PD | Predicate disambiguation | batch_6a01a5dfd628819083c032d8cfd2e726 |
completed | May 11, 2026, 9:48 a.m. |
Created at: May 1, 2026, 2 a.m.