Triple
T638973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plymouth Rock |
E16688
|
entity |
| Predicate | porticoCompleted |
P1574
|
FINISHED |
| Object | 1921 |
—
|
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: 1921 | Statement: [Plymouth Rock, porticoCompleted, 1921]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: porticoCompleted Context triple: [Plymouth Rock, porticoCompleted, 1921]
-
A.
hasPortico
Indicates that one entity (typically a building or structure) features a portico as part of its architectural design.
-
B.
completedIn
chosen
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
C.
closingDoxology
Indicates the concluding liturgical or devotional formula of praise that formally ends a prayer, hymn, or religious text.
-
D.
portfolioOf
Indicates that one entity is the collection of investments, works, or assets that are owned, managed, or represented by another entity.
-
E.
closureProcess
Indicates the procedure or set of actions carried out to formally conclude, finalize, or terminate an ongoing activity, case, or process.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a17b125481909a6ab53424954792 |
completed | March 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69a49d0629308190bcc137639567f7c2 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.