Triple
T23378631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labouchere Amendment |
E593675
|
entity |
| Predicate | excludedFromScope |
P63146
|
FINISHED |
| Object | female homosexual acts |
—
|
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: female homosexual acts | Statement: [Labouchere Amendment, excludedFromScope, female homosexual acts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excludedFromScope Context triple: [Labouchere Amendment, excludedFromScope, female homosexual acts]
-
A.
excludedFrom
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
-
B.
scopeDoesNotInclude
chosen
Indicates that a given scope explicitly excludes or does not cover a particular element, condition, or responsibility.
-
C.
excludeRange
Indicates that certain values, items, or elements falling within a specified range are to be omitted or not considered.
-
D.
exemptedFrom
Indicates that an entity is not subject to, or is formally released from, a rule, obligation, requirement, or liability that would otherwise apply.
-
E.
excludesFromEvidence
Indicates that something is intentionally omitted or disallowed from being considered as evidence in a given context.
- 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3b5e4f0819081a5d4586796677b |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:33 p.m.