Triple
T25923482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooklyn Italians |
E653236
|
entity |
| Predicate | hasEthnicTie |
P87231
|
FINISHED |
| Object | Italian-American community |
—
|
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: Italian-American community | Statement: [Brooklyn Italians, hasEthnicTie, Italian-American community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnicTie Context triple: [Brooklyn Italians, hasEthnicTie, Italian-American community]
-
A.
hasEthnicScope
Indicates that something is relevant or applicable specifically to a particular ethnic group or ethnic context.
-
B.
linkedToEthnicIdentity
chosen
Indicates a relationship where something is associated or connected with a particular ethnic identity.
-
C.
mayBelongToEthnicGroup
Indicates that an entity is possibly, but not certainly, a member of a specified ethnic group.
-
D.
hasEthnolinguisticPresence
Indicates that a particular ethnolinguistic group is present or represented within a specified place, context, or population.
-
E.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 22, 2026, 8:35 a.m.