Triple
T27752851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 6 |
E701255
|
entity |
| Predicate | returnSite |
P91005
|
FINISHED |
| Object | Kazakh Steppe |
—
|
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: Kazakh Steppe | Statement: [Expedition 6, returnSite, Kazakh Steppe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnSite Context triple: [Expedition 6, returnSite, Kazakh Steppe]
-
A.
resolutionSite
Indicates the location, context, or setting where a conflict, issue, or process is brought to a conclusion or resolved.
-
B.
returnService
Indicates a relationship where a service that was previously provided is being sent back, reversed, or requested to be undone or refunded.
-
C.
returnModuleLandingSite
chosen
Indicates the location or site where a returning module is intended to land or touch down.
-
D.
returnsTo
Indicates that an entity goes back to a previous location, state, or entity it was associated with before.
-
E.
servesSite
Indicates that one entity provides or hosts a website or web service for 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 4:21 p.m.