Triple
T8357964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Predpriyatie |
E196725
|
entity |
| Predicate | explorationPurpose |
P82290
|
FINISHED |
| Object | geographical discovery |
—
|
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: geographical discovery | Statement: [Predpriyatie, explorationPurpose, geographical discovery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explorationPurpose Context triple: [Predpriyatie, explorationPurpose, geographical discovery]
-
A.
explorationType
Indicates the specific kind or category of exploration activity associated with an entity or event.
-
B.
explorationSubject
Indicates that an entity is the focus or target of an exploration, investigation, or exploratory activity carried out by another entity.
-
C.
explores
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
-
D.
exploresFor
Indicates that one entity actively investigates or searches within or on behalf of another entity, typically to discover or obtain something for that other entity’s benefit.
-
E.
sunJourneyPurpose
Indicates the purpose or intended goal behind a sun-related journey or movement.
- F. None of above. chosen
Provenance (4 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb806fa5c88190b23b6b3ee9d6ec6d |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:59 p.m.