Triple
T8015783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Philadelphia |
E186610
|
entity |
| Predicate | socialHistoryFeature |
P80579
|
FINISHED |
| Object | Quaker influence |
—
|
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: Quaker influence | Statement: [History of Philadelphia, socialHistoryFeature, Quaker influence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialHistoryFeature Context triple: [History of Philadelphia, socialHistoryFeature, Quaker influence]
-
A.
collectionHistory
Indicates the record of when, how, and from whom an item or set of items was acquired, transferred, or otherwise added to a collection over time.
-
B.
socialFeature
Indicates that one entity provides or participates in a social interaction capability or function involving other entities.
-
C.
sharesHistoryWith
Indicates that two entities have a common or overlapping past, such as shared experiences, events, or origins.
-
D.
sponsorHistory
Indicates that one entity has previously acted as a sponsor for another entity or event over time.
-
E.
viewedHistoryAs
Indicates that one entity has examined or interpreted another entity as a historical record or in the context of its past events.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3df37a00819088780e5461bc5b41 |
completed | March 31, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:20 p.m.