Triple
T16575134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arkoma Basin |
E402689
|
entity |
| Predicate | hasExplorationHistorySince |
P23375
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Arkoma Basin, hasExplorationHistorySince, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExplorationHistorySince Context triple: [Arkoma Basin, hasExplorationHistorySince, early 20th century]
-
A.
hasExploration
Indicates that one entity engages in, is associated with, or possesses an activity or process of exploration in relation to another entity or context.
-
B.
hasTourHistoryWith
Indicates that two entities have previously participated together in one or more tours or touring events.
-
C.
hasTourHistory
Indicates that an entity has a record of past tours or tour-related activities.
-
D.
exploredDuring
chosen
Indicates that an entity was explored or investigated within the time frame or context of a specified event or period.
-
E.
exploredWith
Indicates that one entity explored something together with another entity as companions or partners in the exploration.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3595bbbbc8190b023f4872908c031 |
completed | April 18, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.