Triple
T26439582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reale Albergo dei Poveri, Naples |
E665048
|
entity |
| Predicate | functionOverTime |
P165351
|
FINISHED |
| Object | poorhouse |
—
|
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: poorhouse | Statement: [Reale Albergo dei Poveri, Naples, functionOverTime, poorhouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionOverTime Context triple: [Reale Albergo dei Poveri, Naples, functionOverTime, poorhouse]
-
A.
functionDuringPeriod
Indicates that a function, role, or activity is performed or valid throughout a specified time period.
-
B.
temporalFunction
Indicates that one entity serves as a temporal modifier or function that specifies when, how long, or with what temporal characteristics another event or state occurs.
-
C.
timeSampling
Indicates that one entity specifies how or at what intervals another entity is sampled or measured over time.
-
D.
expandedOverTime
Indicates that something has increased in size, scope, or extent as time has passed.
-
E.
chronologicalFunction
Indicates a temporal relationship where one event or state functions to order, structure, or position another within a sequence of time.
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 26, 2026, 11:57 p.m.