Triple
T29403931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King's Orange Rangers |
E745732
|
entity |
| Predicate | hasEthnicOrPoliticalIdentity |
P87231
|
FINISHED |
| Object | Loyalist |
—
|
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: Loyalist | Statement: [King's Orange Rangers, hasEthnicOrPoliticalIdentity, Loyalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnicOrPoliticalIdentity Context triple: [King's Orange Rangers, hasEthnicOrPoliticalIdentity, Loyalist]
-
A.
ethnicIdentityOf
Indicates that one entity is the ethnic identity or affiliation possessed by another entity.
-
B.
laterEthnicIdentity
Indicates that an entity’s ethnic identity is associated with or applies to a later period in time relative to some earlier state or context.
-
C.
linkedToEthnicIdentity
chosen
Indicates a relationship where something is associated or connected with a particular ethnic identity.
-
D.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
E.
ethnoreligiousIdentity
Indicates a relationship where an entity is characterized by a combined ethnic and religious group identity.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 28, 2026, 2:52 p.m.