Triple
T37753428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas City disaster of 1947 |
E941044
|
entity |
| Predicate | hasHomeless |
P36920
|
FINISHED |
| Object | thousands of residents |
—
|
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: thousands of residents | Statement: [Texas City disaster of 1947, hasHomeless, thousands of residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeless Context triple: [Texas City disaster of 1947, hasHomeless, thousands of residents]
-
A.
hasNumberOfHomeless
chosen
Indicates the quantified count of homeless individuals associated with a given entity or context.
-
B.
estimatedHomeless
Indicates that a person or group is assessed or classified as likely experiencing homelessness, typically based on estimation rather than confirmed status.
-
C.
hasHome
Indicates that an entity possesses or is associated with a place where it lives or is based.
-
D.
hasHousingAccess
Indicates that an entity has the ability, right, or opportunity to obtain or use suitable housing.
-
E.
hasFamilyHomeAt
Indicates that an entity has its family residence or primary household located at a specified place.
- 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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: May 3, 2026, 4:19 p.m.