Triple
T20445016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sue (A Boy Named Sue) |
E501495
|
entity |
| Predicate | hasTraditionallyFeminineName |
P104114
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sue (A Boy Named Sue), hasTraditionallyFeminineName, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionallyFeminineName Context triple: [Sue (A Boy Named Sue), hasTraditionallyFeminineName, true]
-
A.
hasGenderInSomeTraditions
Indicates that, in at least some cultural, religious, or historical traditions, the subject is regarded as having a specific gender.
-
B.
hasFeminineFormInSomeLanguages
Indicates that the referenced entity has a distinct feminine grammatical or lexical form in at least one language.
-
C.
namedForGender
Indicates that one entity is named in a way that reflects or is derived from a particular gender or gender-related characteristic of another entity.
-
D.
genderOfName
chosen
Indicates the gender typically associated with a given name.
-
E.
hasGrammaticalGender
Indicates that one entity assigns or possesses a specific grammatical gender in relation to another entity (such as a word, phrase, or linguistic unit).
- 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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e68cfca4788190ad57ecb504f54d11 |
completed | April 20, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:32 a.m.