Triple
T30175957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hakeem Campbell |
E767057
|
entity |
| Predicate | relationshipProgressionWith |
P87667
|
FINISHED |
| Object | Moesha Mitchell |
E763554
|
NE 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: Moesha Mitchell | Statement: [Hakeem Campbell, relationshipProgressionWith, Moesha Mitchell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipProgressionWith Context triple: [Hakeem Campbell, relationshipProgressionWith, Moesha Mitchell]
-
A.
relationshipDevelopsWith
chosen
Indicates that a relationship grows, evolves, or becomes more developed between two entities over time.
-
B.
relationshipDynamic
Indicates a changing or evolving pattern of interaction between entities, such as shifts in their roles, closeness, or influence over time.
-
C.
relationshipDurationWith
Indicates the length of time that a specified relationship between two entities has existed or is expected to last.
-
D.
relationshipOutcome
Indicates the result or consequence that arises from a particular relationship between two or more entities.
-
E.
relationshipImpact
Indicates how one entity’s relationship with another affects or changes those entities or their interaction.
- F. None of above.
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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a020ab9630c8190a55efd5704cc6043 |
completed | May 11, 2026, 4:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a277bfec8848190ab028b8b53b72ee5 |
completed | June 9, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_6a020800e2b88190a1a37e710d8c92bf |
completed | May 11, 2026, 4:46 p.m. |
Created at: April 29, 2026, 7:25 p.m.