Triple
T30355549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garret Hostel |
E772133
|
entity |
| Predicate | nameSurvivesIn |
P149843
|
FINISHED |
| Object | Garret Hostel Lane |
—
|
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: Garret Hostel Lane | Statement: [Garret Hostel, nameSurvivesIn, Garret Hostel Lane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameSurvivesIn Context triple: [Garret Hostel, nameSurvivesIn, Garret Hostel Lane]
-
A.
namePreservedIn
chosen
Indicates that an entity’s name has been maintained or carried over unchanged within another entity or context.
-
B.
namedIn
Indicates that one entity is explicitly mentioned or referenced by name within another entity (such as a document, statement, or record).
-
C.
namesAs
Indicates that one entity assigns or uses a particular name or label to refer to another entity.
-
D.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
E.
nameLiterallyMeans
Indicates that the literal meaning or direct translation of one entity’s name is given by the other entity.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6823e27d88190af8342b01f9876e8 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:56 p.m.