Triple
T32440833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Henry |
E829009
|
entity |
| Predicate | landingPartyLeader |
P56436
|
FINISHED |
| Object | Captain Christopher Newport |
—
|
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: Captain Christopher Newport | Statement: [Cape Henry, landingPartyLeader, Captain Christopher Newport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingPartyLeader Context triple: [Cape Henry, landingPartyLeader, Captain Christopher Newport]
-
A.
partyLed
chosen
Indicates that one entity serves as the leader or head of a particular party, organization, or group.
-
B.
sponsorParty
Indicates that one party provides support, typically financial or promotional, to another party, often in exchange for association or visibility.
-
C.
lastOrganizer
Indicates that one entity is the most recent or final organizer associated with another entity or event.
-
D.
principalOrganizer
Indicates that an entity serves as the main or leading organizer responsible for planning or coordinating another entity or event.
-
E.
hostCeremony
Indicates that one entity organizes and conducts a formal event or ceremony for or involving another 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2e2652881909198964213886476 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:55 a.m.