Triple
T11033707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shell Grotto |
E260821
|
entity |
| Predicate | hasProposedOrigins |
P97412
|
FINISHED |
| Object | 18th-century folly |
—
|
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: 18th-century folly | Statement: [Shell Grotto, hasProposedOrigins, 18th-century folly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProposedOrigins Context triple: [Shell Grotto, hasProposedOrigins, 18th-century folly]
-
A.
hasProposedOutcome
Indicates that an action, decision, or process is associated with a suggested or anticipated result that is being put forward but not yet realized or confirmed.
-
B.
hasProposedResolution
Indicates that an entity has put forward a specific resolution or solution for consideration or decision regarding another entity or issue.
-
C.
hasProposal
Indicates that an entity possesses, is associated with, or is the subject of a specific proposal.
-
D.
hasProposedLanguage
Indicates that an entity has put forward or suggested a particular language, typically as a candidate for use, adoption, or standardization.
-
E.
hasProposedRole
Indicates that one entity has suggested or put forward a specific role or position for another entity.
- F. None of above. chosen
Provenance (4 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797e709648190adbb05197e15ff76 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:25 p.m.