Triple
T19996001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French nobility |
E494193
|
entity |
| Predicate | couldBeLostBy |
P82574
|
FINISHED |
| Object | derogation |
—
|
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: derogation | Statement: [French nobility, couldBeLostBy, derogation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couldBeLostBy Context triple: [French nobility, couldBeLostBy, derogation]
-
A.
canBeLostBy
chosen
Indicates that something is capable of being lost or forfeited by a particular entity.
-
B.
lostTo
Indicates that one entity was defeated by another in a competition, conflict, or comparison.
-
C.
lostOrDestroyed
Indicates that something has ceased to exist in its original, usable form, either by being misplaced beyond recovery or physically destroyed.
-
D.
isLostBy
Indicates that something ceases to be possessed, controlled, or retained by a particular entity.
-
E.
lostIn
Indicates that an entity has become unable to find its way or is no longer in control or possession within a particular place, situation, or 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe3fb288190a935c334e8a5d54e |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:32 p.m.