Triple
T4460824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape St George Lighthouse ruins |
E98248
|
entity |
| Predicate | inServiceStartDate |
P24583
|
FINISHED |
| Object | 1860s |
—
|
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: 1860s | Statement: [Cape St George Lighthouse ruins, inServiceStartDate, 1860s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inServiceStartDate Context triple: [Cape St George Lighthouse ruins, inServiceStartDate, 1860s]
-
A.
commissionedInService
Indicates that an entity was formally brought into active service or duty within a particular organization, role, or context.
-
B.
inceptionDate
Indicates the date on which an entity, event, or relationship was first created, established, or began to exist.
-
C.
firstYearOfUse
chosen
Indicates the year in which something was first put into use or began being used.
-
D.
ordinationDate
Indicates the date on which an individual was formally ordained to a religious office or role.
-
E.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
- 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35673337c8190b923159791ec27e3 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f65f6448190abfadb2ae5658798 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:34 p.m.