Triple
T20650817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norbert(a) the Norwegian Ridgeback |
E507486
|
entity |
| Predicate | laterRevealedGender |
P132040
|
FINISHED |
| Object | female |
—
|
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: female | Statement: [Norbert(a) the Norwegian Ridgeback, laterRevealedGender, female]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRevealedGender Context triple: [Norbert(a) the Norwegian Ridgeback, laterRevealedGender, female]
-
A.
laterRecognizedGender
chosen
Indicates that an entity’s gender identity, as recognized or recorded at a later time, differs from or updates an earlier recorded gender.
-
B.
playsGender
Indicates that one entity performs or assumes a particular gender role or identity in a given context.
-
C.
hasGenderRole
Indicates that an entity is associated with, or expected to perform, a particular socially defined gender-based role or set of behaviors.
-
D.
genderDepicted
Indicates that the relationship specifies the gender of the entity as it is represented or portrayed in some context.
-
E.
genderConfiguration
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6af21e87c8190835bf2b2ef195626 |
completed | April 20, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.