Triple
T32011082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvey Cheyne Jr. |
E817402
|
entity |
| Predicate | worksAboard |
P181681
|
FINISHED |
| Object | fishing schooner We’re Here |
—
|
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: fishing schooner We’re Here | Statement: [Harvey Cheyne Jr., worksAboard, fishing schooner We’re Here]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksAboard Context triple: [Harvey Cheyne Jr., worksAboard, fishing schooner We’re Here]
-
A.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
B.
workWithin
Indicates that one entity performs its activities or duties inside the boundaries, scope, or context defined by another entity.
-
C.
worksOnAircraft
Indicates that an entity performs work, maintenance, operation, or related tasks on an aircraft.
-
D.
worksFrom
Indicates that an entity performs its work or duties starting from or based at a specified location or source.
-
E.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: May 1, 2026, 12:15 a.m.