Triple
T22354380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon |
E552612
|
entity |
| Predicate | sexualIdentityConcealedFrom |
P147886
|
FINISHED |
| Object | his parents |
—
|
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: his parents | Statement: [Simon, sexualIdentityConcealedFrom, his parents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sexualIdentityConcealedFrom Context triple: [Simon, sexualIdentityConcealedFrom, his parents]
-
A.
publiclyIdentifiesAs
Indicates that an entity openly declares or presents themself to others as having a particular identity or role.
-
B.
hasGenderIdentity
Indicates that an entity identifies with or experiences a particular gender.
-
C.
identityConcealedBy
Indicates that one entity hides, masks, or obscures the true identity of another entity.
-
D.
sexualOrientationRevealedIn
Indicates that an entity’s sexual orientation is disclosed, made known, or becomes apparent within a specified context, medium, or situation.
-
E.
genderIdentityInSources
Indicates that the gender identity of an entity is recorded or referenced in one or more information sources.
- F. None of above. chosen
Provenance (4 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157ceb2308190941f6507e605a612 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:44 p.m.