Triple
T14734445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nina Borowski |
E346166
|
entity |
| Predicate | friendSexualOrientation |
P4324
|
FINISHED |
| Object | gay |
—
|
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: gay | Statement: [Nina Borowski, friendSexualOrientation, gay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: friendSexualOrientation Context triple: [Nina Borowski, friendSexualOrientation, gay]
-
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.
exploresSexualOrientation
Indicates that an entity engages in examining, questioning, or discovering their own or another’s sexual orientation.
-
D.
fictionalSexualOrientation
Indicates that one entity has a sexual orientation that exists only within a fictional or imagined context, rather than in real life.
-
E.
relationshipWithMen
Indicates a relationship or interaction that specifically involves men as one of the parties.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec72ea9348190817efcdaa973d7f7 |
completed | April 14, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:29 a.m.