Triple
T38426296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Powel House |
E903367
|
entity |
| Predicate | useDuringPeriod |
P122857
|
FINISHED |
| Object | social center of colonial Philadelphia |
—
|
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: social center of colonial Philadelphia | Statement: [Powel House, useDuringPeriod, social center of colonial Philadelphia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useDuringPeriod Context triple: [Powel House, useDuringPeriod, social center of colonial Philadelphia]
-
A.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
B.
appliedDuringPeriod
Indicates that an action, condition, or status was in effect throughout a specified time period.
-
C.
functionDuringPeriod
chosen
Indicates that a function, role, or activity is performed or valid throughout a specified time period.
-
D.
usedBetween
Indicates that something serves as a means, medium, or shared resource connecting or operating jointly between two entities.
-
E.
ownedDuring
Indicates that one entity possessed or held ownership of another entity for some or all of a specified time interval.
- 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_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.