Triple
T33688547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamestown Colony ships |
E863108
|
entity |
| Predicate | subsequentArrival |
P4509
|
FINISHED |
| Object | James River, Virginia |
—
|
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: James River, Virginia | Statement: [Jamestown Colony ships, subsequentArrival, James River, Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentArrival Context triple: [Jamestown Colony ships, subsequentArrival, James River, Virginia]
-
A.
subsequentArrivalDate
Indicates that one entity’s arrival date occurs after the arrival date of another related entity.
-
B.
subsequentOrder
chosen
Indicates that one order occurs after or follows another order in sequence.
-
C.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
D.
arrivalOrder
Indicates the relative sequence in which entities arrive, specifying which one comes before or after another.
-
E.
hasSubsequent
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa6708f88190b8589a41d2271ba6 |
completed | May 3, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.