Triple
T26029579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. Marcus Garvey |
E647391
|
entity |
| Predicate | involvesBusiness |
P170340
|
FINISHED |
| Object | shipping company |
—
|
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 company | Statement: [United States v. Marcus Garvey, involvesBusiness, shipping company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesBusiness Context triple: [United States v. Marcus Garvey, involvesBusiness, shipping company]
-
A.
reflectsBusiness
Indicates that one entity mirrors, represents, or corresponds to the business identity, operations, or interests of another entity.
-
B.
concernsBusinessType
Indicates that something is related or applicable to a particular type or category of business.
-
C.
oftenInvolvedWith
Indicates that one entity frequently participates in or is commonly associated with activities, events, or situations involving another entity.
-
D.
hasBusiness
Indicates that one entity owns, operates, or is formally associated with a business entity.
-
E.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 22, 2026, 9:06 a.m.