Triple
T33987265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | How I Found Livingstone |
E871443
|
entity |
| Predicate | sponsorOfExpeditionDescribed |
P92118
|
FINISHED |
| Object | New York Herald |
—
|
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: New York Herald | Statement: [How I Found Livingstone, sponsorOfExpeditionDescribed, New York Herald]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorOfExpeditionDescribed Context triple: [How I Found Livingstone, sponsorOfExpeditionDescribed, New York Herald]
-
A.
expeditionPatron
chosen
Indicates that an entity financially supports or sponsors an expedition or exploratory venture.
-
B.
expeditionPartnerShip
Indicates a collaborative relationship where two or more entities jointly participate in or undertake an expedition together.
-
C.
sponsorTo
Indicates that one entity provides support, funding, or endorsement to another entity, typically to enable or promote the latter’s activities or initiatives.
-
D.
expeditionMemberOf
Indicates that an entity participates as a member in a specific expedition.
-
E.
shipSponsor
Indicates that one entity serves as the sponsor or patron responsible for supporting, endorsing, or funding a particular ship.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7038f8f2081909a5af9c8b810f597 |
completed | May 3, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f70101ba1c819099380274e6df9a4d |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:50 a.m.