Triple
T5736681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fantine |
E126518
|
entity |
| Predicate | dismissalReason |
P41278
|
FINISHED |
| Object | having an illegitimate child |
—
|
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: having an illegitimate child | Statement: [Fantine, dismissalReason, having an illegitimate child]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dismissalReason Context triple: [Fantine, dismissalReason, having an illegitimate child]
-
A.
reasonForDismissal
chosen
Indicates the cause or justification for which an entity (such as a person, case, or item) was dismissed, terminated, or removed.
-
B.
reasonForDecline
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
-
C.
rejectedJustification
Indicates that a proposed justification or reason offered in a context (e.g., argument, decision, or claim) has been evaluated and not accepted as valid or sufficient.
-
D.
reasonForAnnulment
Indicates the specific cause or grounds on which a prior decision, agreement, or status is formally annulled or declared invalid.
-
E.
suspensionReason
Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0255ad6f48190977bf4f037110aa3 |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:47 p.m.