Triple
T24176470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endurance Expedition |
E599295
|
entity |
| Predicate | rescuerCommander |
P79589
|
FINISHED |
| Object | Luis Pardo |
—
|
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: Luis Pardo | Statement: [Endurance Expedition, rescuerCommander, Luis Pardo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rescuerCommander Context triple: [Endurance Expedition, rescuerCommander, Luis Pardo]
-
A.
escortCommander
Indicates that one entity serves as the commanding officer responsible for leading or overseeing an escort force or mission involving another entity.
-
B.
seeksToRescue
Indicates an entity’s intention or effort to save or free another entity from danger, harm, or an undesirable situation.
-
C.
rescueCoordinatedBy
chosen
Indicates that a rescue operation is organized, directed, or managed by a particular coordinating entity.
-
D.
sideCommander
Indicates that an entity serves as the commanding officer or leader in charge of a particular side or faction in a conflict, operation, or organization.
-
E.
rescuedBy
Indicates that one entity has been saved or brought out of danger by 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:34 p.m.