Triple
T18834483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nic |
E460621
|
entity |
| Predicate | sexualOrientationDepictedAs |
P4324
|
FINISHED |
| Object | non-problematic |
—
|
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: non-problematic | Statement: [Nic, sexualOrientationDepictedAs, non-problematic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sexualOrientationDepictedAs Context triple: [Nic, sexualOrientationDepictedAs, non-problematic]
-
A.
sexualOrientation
chosen
Indicates an entity’s enduring pattern of romantic or sexual attraction toward others, typically in terms of the genders or sexes to which it is attracted.
-
B.
sexualOrientationRevealedIn
Indicates that an entity’s sexual orientation is disclosed, made known, or becomes apparent within a specified context, medium, or situation.
-
C.
genderDepicted
Indicates that the relationship specifies the gender of the entity as it is represented or portrayed in some context.
-
D.
depictsSex
Indicates that one entity visually represents or portrays sexual activity or sexual content involving another entity.
-
E.
hasSexualityCharacteristic
Indicates that an entity possesses a specific sexual orientation or sexuality-related characteristic.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99c1394819095c62eef040e552c |
completed | April 20, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.