Triple
T35208180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dis-arm-her |
E1016596
|
entity |
| Predicate | usedByRealName |
P193276
|
FINISHED |
| Object | Rebecca Quin |
—
|
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: Rebecca Quin | Statement: [Dis-arm-her, usedByRealName, Rebecca Quin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByRealName Context triple: [Dis-arm-her, usedByRealName, Rebecca Quin]
-
A.
notRealNameOf
Indicates that the referenced name is not the entity’s actual or official name (e.g., it is false, fabricated, or otherwise not the real name of that entity).
-
B.
incorrectInformalUsageOfName
Indicates that one entity uses another entity’s name in an informal context in a way that is considered incorrect or inappropriate.
-
C.
realName
Indicates that one entity is the actual, full, or birth name of another entity, which may be known by an alias, nickname, or alternate identity.
-
D.
usedByPersonalName
Indicates that something (such as an object, resource, or identifier) is used by a person identified by a specific personal name.
-
E.
usedByPerson
Indicates that something (such as an object, tool, or resource) is utilized or employed by a person.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
| PDg | Predicate description generation | batch_69fd3d45ccb8819082f15e60bd33afc9 |
completed | May 8, 2026, 1:32 a.m. |
Created at: May 3, 2026, 4:02 p.m.