Triple
T21816054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rich Girl |
E538607
|
entity |
| Predicate | usesSecondPersonAddress |
P63462
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rich Girl, usesSecondPersonAddress, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSecondPersonAddress Context triple: [Rich Girl, usesSecondPersonAddress, yes]
-
A.
usesMailingAddressOf
Indicates that one entity uses another entity’s mailing address as its own for receiving mail or official correspondence.
-
B.
secondPersonForm
chosen
Indicates that an expression is inflected or formulated to address the listener directly, using second-person grammatical form.
-
C.
addressedFor
Indicates that something is directed, designated, or intended for a particular recipient or target.
-
D.
usesAddressingSystem
Indicates that one entity employs or applies a particular addressing system associated with another entity.
-
E.
addresseeOf
Indicates that one entity is the intended recipient or target audience of a communication, message, or expression from 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07ccac9f08190b835ee7a40ecf4c2 |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:54 p.m.