Triple
T30487706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Britski |
E775765
|
entity |
| Predicate | hasEthnicReference |
P27835
|
FINISHED |
| Object | Polish-Americans |
—
|
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: Polish-Americans | Statement: [New Britski, hasEthnicReference, Polish-Americans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnicReference Context triple: [New Britski, hasEthnicReference, Polish-Americans]
-
A.
hasEthnicScope
Indicates that something is relevant or applicable specifically to a particular ethnic group or ethnic context.
-
B.
hasEthnicCharacteristic
chosen
Indicates that an entity possesses or is associated with a particular ethnic characteristic or identity.
-
C.
hasEthnicInfluence
Indicates that one entity has a cultural, traditional, or ethnic impact on, or contributes to shaping the ethnic character of, another entity.
-
D.
hasEthnicTarget
Indicates that an action, statement, or event is directed toward or targets a specific ethnic group.
-
E.
hasEthnicNameType
Indicates that an entity’s name is classified according to a specific ethnic or cultural naming type.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 29, 2026, 8:13 p.m.