Triple
T21787610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astrolabe |
E537880
|
entity |
| Predicate | geographicFocusOfExploration |
P120407
|
FINISHED |
| Object | Pacific region |
—
|
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: Pacific region | Statement: [Astrolabe, geographicFocusOfExploration, Pacific region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicFocusOfExploration Context triple: [Astrolabe, geographicFocusOfExploration, Pacific region]
-
A.
countryOfExploration
Indicates the country under whose auspices or within whose territory an exploration activity was conducted.
-
B.
explores
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
-
C.
majorExplorationIn
Indicates that an entity’s primary field of exploration, investigation, or study is within a specified domain or area.
-
D.
notableExplorationRegion
chosen
Indicates that an entity is recognized for significant exploration activities or discoveries within a particular geographic region.
-
E.
geographyBehavior
Indicates how an entity behaves, functions, or interacts in relation to its geographic context or location.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0621c68588190977891055e80a499 |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.