Triple
T36136022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerry’s apartment building |
E1045168
|
entity |
| Predicate | hasApartment |
P196192
|
FINISHED |
| Object | Jerry Seinfeld’s apartment |
—
|
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: Jerry Seinfeld’s apartment | Statement: [Jerry’s apartment building, hasApartment, Jerry Seinfeld’s apartment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApartment Context triple: [Jerry’s apartment building, hasApartment, Jerry Seinfeld’s apartment]
-
A.
hasHousingArrangement
Indicates that an entity has a specific type or status of housing or living arrangement in relation to another entity or context.
-
B.
hasHouse
Indicates that one entity possesses, owns, or is provided with a house in relation to another entity.
-
C.
hasHouseWithin
Indicates that one entity possesses or is associated with a house that is located within the spatial or administrative boundaries of another entity.
-
D.
hasHome
Indicates that an entity possesses or is associated with a place where it lives or is based.
-
E.
hasHouses
Indicates that one entity possesses, controls, or contains one or more houses in relation to another entity or context.
- 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_69f76e36a4508190b5bfc8f594272a4c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
| PDg | Predicate description generation | batch_69fe12a769c08190bc445d302d2e8f98 |
completed | May 8, 2026, 4:43 p.m. |
Created at: May 3, 2026, 4:08 p.m.