Triple
T28117787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brown, Brothers & Co. (New York) ship Eliza Frances crew |
E710685
|
entity |
| Predicate | hasShipOwner |
P173238
|
FINISHED |
| Object | Brown, Brothers & Co. (New York) |
—
|
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: Brown, Brothers & Co. (New York) | Statement: [Brown, Brothers & Co. (New York) ship Eliza Frances crew, hasShipOwner, Brown, Brothers & Co. (New York)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShipOwner Context triple: [Brown, Brothers & Co. (New York) ship Eliza Frances crew, hasShipOwner, Brown, Brothers & Co. (New York)]
-
A.
hasShipName
Indicates that an entity (such as a vessel or record) is associated with a specific ship name.
-
B.
hasShipRole
Indicates that an entity holds or is assigned a specific role or function on a ship.
-
C.
shipCompany
Indicates that one entity is the shipping company responsible for transporting goods or providing shipping services for another entity.
-
D.
shipFlag
Indicates that a ship is registered under and legally operates under the authority of a specified national flag or registry.
-
E.
shipNameWith
Indicates that a ship is associated with or identified by a particular name.
- 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 27, 2026, 9:15 p.m.