Triple
T5068756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Cobra |
E114211
|
entity |
| Predicate | hasPersona |
P61233
|
FINISHED |
| Object | cobra-themed persona |
—
|
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: cobra-themed persona | Statement: [Lady Cobra, hasPersona, cobra-themed persona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPersona Context triple: [Lady Cobra, hasPersona, cobra-themed persona]
-
A.
hasPerson
Indicates that an entity is associated with or includes a specific person.
-
B.
hasFrontPerson
Indicates that an entity is represented, led, or fronted publicly by a specific person.
-
C.
hasNotablePersonAsFace
Indicates that an entity is publicly represented or symbolized by a specific notable person, such as a spokesperson, ambassador, or brand face.
-
D.
appliesToPerson
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific person.
-
E.
hasPar
Indicates a relationship where one entity has another entity as its parent.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd749dd1a08190858fa739df024eb4 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd73d90b608190bd6c2407e84e2b64 |
completed | March 20, 2026, 4:20 p.m. |
Created at: March 20, 2026, 1:39 p.m.