Triple
T28799029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinchgut Island |
E727174
|
entity |
| Predicate | constructionOfFortStarted |
P165636
|
FINISHED |
| Object | mid-19th century |
—
|
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: mid-19th century | Statement: [Pinchgut Island, constructionOfFortStarted, mid-19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionOfFortStarted Context triple: [Pinchgut Island, constructionOfFortStarted, mid-19th century]
-
A.
constructionBeganAsFortressIn
Indicates that the construction of something originally began with the purpose or function of serving as a fortress at a specified time or in a specified place.
-
B.
fortificationBuilt
chosen
Indicates that a fortification was constructed or established, linking the structure to the event or agent responsible for its building.
-
C.
bunkerConstructionStart
Indicates the point in time when construction work on a bunker begins.
-
D.
buildingConstructionStart
Indicates the point in time when the construction work on a building begins.
-
E.
monumentConstructionStart
Indicates the date or time when the construction of a monument was begun.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 28, 2026, 6:26 a.m.