Triple
T9874142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iranian Armenian Americans |
E240030
|
entity |
| Predicate | maintainsDistinctIdentityFrom |
P1612
|
FINISHED |
| Object | other Iranian Americans |
—
|
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: other Iranian Americans | Statement: [Iranian Armenian Americans, maintainsDistinctIdentityFrom, other Iranian Americans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainsDistinctIdentityFrom Context triple: [Iranian Armenian Americans, maintainsDistinctIdentityFrom, other Iranian Americans]
-
A.
hasDistinctIdentity
Indicates that an entity possesses its own unique, distinguishable identity separate from other entities.
-
B.
isDistinctFrom
chosen
Indicates that two entities are not identical and can be clearly distinguished from one another.
-
C.
endOfDistinctIdentity
Indicates the point or condition at which a previously separate or distinguishable identity ceases to exist as a distinct entity.
-
D.
isDistinguishedBy
Indicates that one entity is characterized or set apart from others by a particular feature, quality, or attribute.
-
E.
hasIdentity
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
- 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_69ca84e8a0788190b9061811d50fd554 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3f89fa081908b58956902c193cf |
completed | April 2, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:37 p.m.