Triple
T1567105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philadelphia Mint |
E33455
|
entity |
| Predicate | numberOfBuildingsInHistory |
P11484
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Philadelphia Mint, numberOfBuildingsInHistory, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfBuildingsInHistory Context triple: [Philadelphia Mint, numberOfBuildingsInHistory, 4]
-
A.
historicalStructure
Indicates that the subject is a structure recognized for its historical significance or heritage value.
-
B.
architectureHistory
Indicates a historical or developmental relationship between an entity and its architectural evolution, style, or significant architectural events over time.
-
C.
numberOfBuildings
chosen
Indicates the total count of buildings associated with a given entity or within a specified context.
-
D.
residenceHistoric
Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
-
E.
capitalHistoric
Indicates that a location has served as a capital city at some point in history, even if it is not the current capital.
- 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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90fccd4b48190a44012888a00af7f |
completed | March 5, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69a907b872f0819096b3df6ad502c63e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.