Triple
T3067188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viola de Lesseps |
E62130
|
entity |
| Predicate | forbiddenTo |
P38719
|
FINISHED |
| Object | act publicly as a woman |
—
|
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: act publicly as a woman | Statement: [Viola de Lesseps, forbiddenTo, act publicly as a woman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forbiddenTo Context triple: [Viola de Lesseps, forbiddenTo, act publicly as a woman]
-
A.
isProhibitedFor
chosen
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
-
B.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
C.
restrictedFromUseFor
Indicates that something is prohibited or limited from being used for a specified purpose, context, or application.
-
D.
doesNotAllow
Indicates that one entity prevents, forbids, or does not permit another entity from performing a specific action or being in a certain state.
-
E.
excludedFrom
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada0fea06881909e5251eea26599ac |
completed | March 8, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69ad9624b7a0819091d255614f5819ea |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.