Triple
T24287889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reed, Henderson and Smart |
E605720
|
entity |
| Predicate | notableWorkCity |
P90664
|
FINISHED |
| Object | Melbourne |
—
|
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: Melbourne | Statement: [Reed, Henderson and Smart, notableWorkCity, Melbourne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkCity Context triple: [Reed, Henderson and Smart, notableWorkCity, Melbourne]
-
A.
notableCityOfOperation
Indicates that a city is a primary or particularly significant location where an entity conducts its operations or activities.
-
B.
notablePlaceOfWork
chosen
Indicates that there is a notable or significant place where the entity has worked or been employed.
-
C.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
-
D.
notableCityIncluded
Indicates that a notable or significant city is contained within, or is part of, a larger geographic or administrative entity.
-
E.
alsoKnownForCity
Indicates that an entity is additionally recognized or notable for its association with a particular city.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f57a9a08190b183879ff76071d0 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.