Triple
T15405692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christmas Tree Lane Historic District |
E368446
|
entity |
| Predicate | contributingResourceType |
P118672
|
FINISHED |
| Object | site |
—
|
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: site | Statement: [Christmas Tree Lane Historic District, contributingResourceType, site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contributingResourceType Context triple: [Christmas Tree Lane Historic District, contributingResourceType, site]
-
A.
sharesResourceType
Indicates that two or more entities use or are associated with the same type or category of resource.
-
B.
contributeTo
Indicates that one entity provides support, resources, or effort that helps bring about, enhance, or maintain another entity, outcome, or state.
-
C.
primaryResourceType
Indicates the main or predominant type/category of resource associated with an entity or activity.
-
D.
recognizesContributionType
Indicates that an entity acknowledges or identifies a specific type or category of contribution made by another entity.
-
E.
tributeTo
Indicates that one entity is created, given, or dedicated as a mark of respect, admiration, or honor toward 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8fde64819082ec0c68df305561 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:20 a.m.