Triple
T27356839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamestown Rediscovery project |
E685706
|
entity |
| Predicate | notableDiscoveryContext |
P136919
|
FINISHED |
| Object | remains of James Fort |
—
|
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: remains of James Fort | Statement: [Jamestown Rediscovery project, notableDiscoveryContext, remains of James Fort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDiscoveryContext Context triple: [Jamestown Rediscovery project, notableDiscoveryContext, remains of James Fort]
-
A.
discoveryNote
chosen
Indicates that there is a note or annotation providing additional information or context about a particular discovery.
-
B.
notableDiscoveryAtSite
Indicates that an entity is recognized for having made an important discovery at a particular site.
-
C.
historicalDiscovery
Indicates that one entity is the discoverer or originator of another entity in a historical context, capturing the act of first finding, identifying, or documenting it.
-
D.
notableExplorer
Indicates that the subject is recognized for significant achievements or prominence in the field of exploration.
-
E.
discoveriesInclude
Indicates that one entity’s set of discoveries contains or encompasses the other entity as a discovered item.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
Created at: April 27, 2026, 11:51 a.m.