Triple
T25782179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archewell, Inc. |
E649318
|
entity |
| Predicate | hasKeyPeople |
P2308
|
FINISHED |
| Object | Prince Harry, Duke of Sussex |
—
|
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: Prince Harry, Duke of Sussex | Statement: [Archewell, Inc., hasKeyPeople, Prince Harry, Duke of Sussex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyPeople Context triple: [Archewell, Inc., hasKeyPeople, Prince Harry, Duke of Sussex]
-
A.
hasPeopleName
Indicates that an entity is associated with a specific person's name.
-
B.
hasPerson
chosen
Indicates that an entity is associated with or includes a specific person.
-
C.
hasPersona
Indicates that an entity possesses or is associated with a particular persona, role, or character profile.
-
D.
hasKeyWork
Indicates that an entity possesses or is associated with a primary or central work (such as a main publication, artwork, or project) that is especially representative or important.
-
E.
hasKeyAccord
Indicates that one entity possesses or defines the primary key or governing agreement that authorizes or controls another entity.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 22, 2026, 5:51 a.m.