Triple
T37056837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Objectum Sexuality |
E917212
|
entity |
| Predicate | facesSocialChallenge |
P183865
|
FINISHED |
| Object | stigma |
—
|
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: stigma | Statement: [Objectum Sexuality, facesSocialChallenge, stigma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facesSocialChallenge Context triple: [Objectum Sexuality, facesSocialChallenge, stigma]
-
A.
challengeTo
Indicates that one entity issues a challenge or dare for another entity to face or respond to.
-
B.
challengeFor
chosen
Indicates that one entity presents a difficulty, test, or obstacle that must be faced or overcome by another entity.
-
C.
activityChallenged
Indicates that one entity has questioned, disputed, or formally contested the validity, appropriateness, or outcome of an activity involving another entity.
-
D.
challengeType
Indicates the specific category or kind of challenge associated with an action or relationship between entities.
-
E.
featuredChallengeCup
Indicates that a particular Challenge Cup is highlighted or given special prominence relative to others.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.