Triple
T3052296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyclone Tracy |
E60397
|
entity |
| Predicate | homelessPeople |
P36920
|
FINISHED |
| Object | approximately 25,000 |
—
|
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: approximately 25,000 | Statement: [Cyclone Tracy, homelessPeople, approximately 25,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homelessPeople Context triple: [Cyclone Tracy, homelessPeople, approximately 25,000]
-
A.
estimatedHomeless
Indicates that a person or group is assessed or classified as likely experiencing homelessness, typically based on estimation rather than confirmed status.
-
B.
hasNumberOfHomeless
chosen
Indicates the quantified count of homeless individuals associated with a given entity or context.
-
C.
positionOnWelfare
Indicates a stance or viewpoint an entity holds regarding welfare policies or welfare-related issues.
-
D.
displacedPeopleEstimate
Indicates an estimated number of people who have been forced to leave their homes or usual places of residence due to a particular event or situation.
-
E.
welfareConcern
Indicates that one entity has a concern, issue, or responsibility related to the welfare or well-being of another 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9bf3c52c8190bbe8e5cb98c21715 |
completed | March 8, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.