Triple
T11893339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timão |
E282972
|
entity |
| Predicate | genderInPortuguese |
P92437
|
FINISHED |
| Object | masculine noun |
—
|
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: masculine noun | Statement: [Timão, genderInPortuguese, masculine noun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderInPortuguese Context triple: [Timão, genderInPortuguese, masculine noun]
-
A.
hasGenderInPortuguese
chosen
Indicates that a term or entity is associated with a specific grammatical gender in the Portuguese language.
-
B.
genderConfiguration
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
-
C.
genderCategories
Indicates the classification of an entity into one or more gender-related categories or identities.
-
D.
genderDivision
Indicates a relationship where roles, responsibilities, or categories are separated or distinguished based on gender.
-
E.
genderSignificance
Indicates the relevance or impact that an entity’s gender has within a particular context, relationship, or interpretation.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8dd1172988190a2c13d37220f2f93 |
completed | April 10, 2026, 11:20 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.