Triple
T27974027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amirabad neighborhood |
E706437
|
entity |
| Predicate | hasTypicalResident |
P189337
|
FINISHED |
| Object | university students |
—
|
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: university students | Statement: [Amirabad neighborhood, hasTypicalResident, university students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalResident Context triple: [Amirabad neighborhood, hasTypicalResident, university students]
-
A.
hasNotableResident
Indicates that an entity is or has been a well-known or distinguished resident of a particular place or location.
-
B.
hasNonHumanResident
Indicates that a place or location is inhabited or occupied by one or more non-human entities.
-
C.
hasResidentPopulation
Indicates that a place or administrative area has a population of people who live there permanently or for an extended period.
-
D.
coResident
Indicates that two or more entities live in the same residence or dwelling at the same time.
-
E.
hasOccupationOfResident
Indicates that one entity holds the role or status of being a resident 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: April 27, 2026, 7:40 p.m.