Triple
T36546819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gift of Men |
E901160
|
entity |
| Predicate | doesNotApplyToRace |
P73176
|
FINISHED |
| Object | Elves |
—
|
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: Elves | Statement: [Gift of Men, doesNotApplyToRace, Elves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotApplyToRace Context triple: [Gift of Men, doesNotApplyToRace, Elves]
-
A.
doesNotGenerallyApplyTo
Indicates that a rule, property, or condition is typically not relevant or applicable to the referenced entity or situation in most cases.
-
B.
doNotApplyTo
chosen
Indicates that something is excluded from affecting, covering, or being relevant to a specified target or case.
-
C.
doesNotApplyIf
Indicates that a rule, condition, or effect is not valid or should not be enforced when a specified circumstance or exception is present.
-
D.
doesNotParticipateIn
Indicates that an entity is explicitly not involved in, associated with, or taking part in a specified activity, event, or process.
-
E.
nonEligibility
Indicates that an entity does not meet the required conditions or criteria to qualify for a specified status, benefit, or action.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.