Triple
T24792988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Place for Us |
E620300
|
entity |
| Predicate | hasImmigrantGroup |
P70257
|
FINISHED |
| Object | Greek immigrants |
—
|
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: Greek immigrants | Statement: [A Place for Us, hasImmigrantGroup, Greek immigrants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImmigrantGroup Context triple: [A Place for Us, hasImmigrantGroup, Greek immigrants]
-
A.
hasImmigrantCommunitiesFrom
chosen
Indicates that a place or region contains established communities of people who have immigrated from a specified origin location.
-
B.
immigratedTo
Indicates that an entity moved from its country of origin to live permanently in another specified country or region.
-
C.
immigratedDuring
Indicates that an entity moved to and settled in a new country or region during a specified time period.
-
D.
hasNotableEmigrant
Indicates that an entity has at least one emigrant who is considered notable or significant in some recognized way.
-
E.
hasSignificantEmigrationTo
Indicates that a substantial number of people leave one place, group, or entity to move and settle in another specific place, group, or 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f41104fdd48190aa8c879738d8845b |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:47 a.m.