Triple
T11047320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harad |
E261165
|
entity |
| Predicate | hasNotablePeople |
P97477
|
FINISHED |
| Object | Haradrim chieftains |
—
|
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: Haradrim chieftains | Statement: [Harad, hasNotablePeople, Haradrim chieftains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePeople Context triple: [Harad, hasNotablePeople, Haradrim chieftains]
-
A.
holderNotableFor
Indicates that a holder (such as a person or organization) is particularly known or recognized for a specific role, achievement, work, or characteristic.
-
B.
hasNotablePersonAsFace
Indicates that an entity is publicly represented or symbolized by a specific notable person, such as a spokesperson, ambassador, or brand face.
-
C.
hasNotablePersonBornHere
Indicates that a notable or distinguished person was born at the referenced place.
-
D.
hasNotablePersonConnection
Indicates that there exists a significant or noteworthy personal, professional, or historical relationship between the subject and the referenced person.
-
E.
hasNotableHonoree
Indicates that an entity is notably dedicated to, named after, or honors a particular person or group.
- F. None of above. chosen
Provenance (4 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798315b988190bc565581b2664009 |
completed | April 9, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.