Triple
T4040046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tristán de Luna y Arellano |
E83923
|
entity |
| Predicate | expeditionCharacterization |
P35090
|
FINISHED |
| Object | ill-fated |
—
|
LITERAL FINISHED |
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: ill-fated | Statement: [Tristán de Luna y Arellano, expeditionCharacterization, ill-fated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expeditionCharacterization Context triple: [Tristán de Luna y Arellano, expeditionCharacterization, ill-fated]
-
A.
describesExpedition
chosen
Indicates that one entity provides a detailed account or characterization of an expedition undertaken by another entity.
-
B.
explores
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
-
C.
typicalExpeditionMode
Indicates the usual or most common mode or method by which an expedition is conducted.
-
D.
expeditionObjective
Indicates the primary goal or purpose that an expedition is intended to achieve.
-
E.
scopeCharacterization
Indicates how the extent, boundaries, or coverage of something is defined, described, or qualified in relation to another entity or context.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb39400881909d0f5430f04e441c |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.