Triple
T30732139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carolina (colony) |
E782450
|
entity |
| Predicate | earlierExploredBy |
P180159
|
FINISHED |
| Object | Spanish explorers |
—
|
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: Spanish explorers | Statement: [Carolina (colony), earlierExploredBy, Spanish explorers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierExploredBy Context triple: [Carolina (colony), earlierExploredBy, Spanish explorers]
-
A.
exploredWith
Indicates that one entity explored something together with another entity as companions or partners in the exploration.
-
B.
isExploredThrough
Indicates that something is examined, investigated, or understood by means of a particular method, process, or medium.
-
C.
willBeExploredBy
Indicates that something is expected or planned to be examined, investigated, or studied by a particular agent in the future.
-
D.
exploredDuring
Indicates that an entity was explored or investigated within the time frame or context of a specified event or period.
-
E.
furtherExploredIn
Indicates that a subject has been examined or developed in greater detail within another work, source, or context.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f73221eef88190bd8905e6e9f5a586 |
completed | May 3, 2026, 11:31 a.m. |
Created at: April 29, 2026, 8:37 p.m.