Triple
T8606424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Browse Basin |
E203808
|
entity |
| Predicate | explorationStarted |
P83837
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Browse Basin, explorationStarted, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explorationStarted Context triple: [Browse Basin, explorationStarted, 1960s]
-
A.
explorationStatus
Indicates the current state or phase of an exploration process or activity between entities.
-
B.
exploredDuring
Indicates that an entity was explored or investigated within the time frame or context of a specified event or period.
-
C.
explored
Indicates that an entity has traveled through, examined, or investigated another entity or area, typically 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.
explorationType
Indicates the specific kind or category of exploration activity associated with an entity or event.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46eabe2c8190a2d13c353055a785 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:25 p.m.