Triple
T12858904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Cod Revival |
E307530
|
entity |
| Predicate | entryDetail |
P33785
|
FINISHED |
| Object | simple portico |
—
|
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: simple portico | Statement: [Cape Cod Revival, entryDetail, simple portico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryDetail Context triple: [Cape Cod Revival, entryDetail, simple portico]
-
A.
recordDetail
Indicates that one entity stores or documents specific information or attributes about another entity.
-
B.
entryFor
Indicates that one entity serves as the specific record, representation, or listing corresponding to another entity.
-
C.
openingDetail
chosen
Indicates the specific manner, context, or characteristics of how an opening (such as a beginning, start, or initial access point) occurs or is carried out between entities.
-
D.
outputDetail
Indicates that one entity specifies the level, amount, or granularity of information or results produced by another entity.
-
E.
layoutDetail
Indicates the specific arrangement or configuration details of how elements are laid out in relation to each other.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:37 p.m.