Triple
T29444549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edison mansion |
E746812
|
entity |
| Predicate | hasTimePeriodVersion |
P159623
|
FINISHED |
| Object | Edison mansion (past – colonial era) |
—
|
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: Edison mansion (past – colonial era) | Statement: [Edison mansion, hasTimePeriodVersion, Edison mansion (past – colonial era)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimePeriodVersion Context triple: [Edison mansion, hasTimePeriodVersion, Edison mansion (past – colonial era)]
-
A.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
B.
hasPeriodRange
Indicates that there is a temporal span or interval during which something is valid, active, or applicable.
-
C.
timeDependentVersionOf
chosen
Indicates that one entity is a version of another whose validity, characteristics, or applicability explicitly depend on a specific point or interval in time.
-
D.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
-
E.
hasAlterationPeriod
Indicates that an entity is associated with a specific time span during which changes, modifications, or alterations may occur or are valid.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 28, 2026, 3:26 p.m.