Triple
T26085816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embley Park |
E657976
|
entity |
| Predicate | historicResident |
P180922
|
FINISHED |
| Object | Florence Nightingale |
—
|
NE NERFINISHED |
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: Florence Nightingale | Statement: [Embley Park, historicResident, Florence Nightingale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicResident Context triple: [Embley Park, historicResident, Florence Nightingale]
-
A.
historicFor
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
B.
historicalHeir
Indicates that one entity is recognized as the successor or inheritor of another in a historical or dynastic context.
-
C.
residenceHistoric
Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
-
D.
historicallyRich
Indicates that an entity possesses significant historical depth, importance, or a wealth of notable past events and heritage.
-
E.
historicallyInhabitedBy
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 26, 2026, 7:42 p.m.