Triple
T22973073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Secret Life of Us |
E571239
|
entity |
| Predicate | locationOfApartmentBlock |
P118211
|
FINISHED |
| Object | St Kilda beachfront |
—
|
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: St Kilda beachfront | Statement: [The Secret Life of Us, locationOfApartmentBlock, St Kilda beachfront]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfApartmentBlock Context triple: [The Secret Life of Us, locationOfApartmentBlock, St Kilda beachfront]
-
A.
locatedInSectionOfBuilding
Indicates that one entity is situated within a specific section or area of a building.
-
B.
locationProperty
Indicates that one entity specifies or characterizes a locational attribute or spatial property of another entity.
-
C.
roofLocation
Indicates that one entity is located on, at, or forming the roof of another entity.
-
D.
buildingLocatedInNeighborhood
chosen
Indicates that a specific building is situated within a particular neighborhood.
-
E.
locationInArchitecture
Indicates the spatial position or placement of one architectural element or feature within or relative to another architectural structure or context.
- 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_69e245b2c6548190a0e4c7f2f7df2d48 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182343a448190a5259cdf721c9d04 |
completed | April 29, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:48 p.m.