Triple
T24713249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blida-Joinville Psychiatric Hospital |
E612084
|
entity |
| Predicate | employedUntil |
P3070
|
FINISHED |
| Object | Frantz Fanon, 1956 |
—
|
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: Frantz Fanon, 1956 | Statement: [Blida-Joinville Psychiatric Hospital, employedUntil, Frantz Fanon, 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employedUntil Context triple: [Blida-Joinville Psychiatric Hospital, employedUntil, Frantz Fanon, 1956]
-
A.
employedAfter
Indicates that one entity became employed by another entity at a point in time later than a referenced employment event or period.
-
B.
employedAtTime
Indicates that an employment relationship holds during a specified time or time interval.
-
C.
hadOccupationStatusUntil
chosen
Indicates that an entity held a particular occupational status up to, but not necessarily beyond, a specified point in time.
-
D.
employedTo
Indicates that one entity is hired or engaged to perform work, services, or duties for another entity.
-
E.
retirementDate
Indicates the date on which an entity stops its active role or service, typically marking the end of its professional or operational period.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:25 a.m.