Triple
T38366027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Queen Charlotte |
E892442
|
entity |
| Predicate | capturedOnDate |
P38643
|
FINISHED |
| Object | 1813-09-10 |
—
|
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: 1813-09-10 | Statement: [USS Queen Charlotte, capturedOnDate, 1813-09-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capturedOnDate Context triple: [USS Queen Charlotte, capturedOnDate, 1813-09-10]
-
A.
capturedAt
Indicates the specific time or moment at which an entity was captured, recorded, or taken.
-
B.
hasCaptureDate
chosen
Indicates the date on which something (such as an image, video, or data sample) was originally captured or recorded.
-
C.
recordedOnDate
Indicates the specific calendar date on which an event, action, or piece of information was formally recorded.
-
D.
photographTakenAt
Indicates that a photograph was captured at a specific location or during a particular event or time.
-
E.
capturedDuring
Indicates that one event or state occurred within the temporal span of another, typically representing that something was recorded, seized, or documented while a specific situation or activity was taking place.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcc7a4d7f881908b43b960911b81e9 |
completed | May 7, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69fcc589720c819089c8f500fea3c86a |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:31 p.m.