Triple
T19999097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition Unknown |
E494270
|
entity |
| Predicate | typicalEpisodeElement |
P51458
|
FINISHED |
| Object | on-site exploration |
—
|
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: on-site exploration | Statement: [Expedition Unknown, typicalEpisodeElement, on-site exploration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEpisodeElement Context triple: [Expedition Unknown, typicalEpisodeElement, on-site exploration]
-
A.
typicalEpisodeContent
chosen
Indicates that the specified content is characteristic or commonly found within episodes of the given series or program.
-
B.
narrativeEpisode
Indicates that one event, scene, or segment functions as a distinct episode within a larger narrative or storyline.
-
C.
narratesEpisode
Indicates that one entity tells or recounts a specific episode or event involving another entity.
-
D.
isEpisodeOfType
Indicates that an episode belongs to or is classified under a specific type or category.
-
E.
typicalProgramElement
Indicates that one program element is a representative or characteristic example of another program element or category of elements.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a09bdc819083305b08a11c6e34 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:32 p.m.