Triple
T36223348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fleury 91 (women) |
E1047915
|
entity |
| Predicate | subjectToTransferWindows |
P76945
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fleury 91 (women), subjectToTransferWindows, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToTransferWindows Context triple: [Fleury 91 (women), subjectToTransferWindows, true]
-
A.
transferPeriod
Indicates the time span or interval during which a transfer from one entity to another takes place.
-
B.
hasTransferWindow
chosen
Indicates that there is a defined time period during which a transfer or movement between entities is allowed or can occur.
-
C.
transferredUnder
Indicates that something is moved, conveyed, or reassigned from one party, context, or control to another under specified terms or conditions.
-
D.
accessibleTransfer
Indicates that a transfer between entities can be performed in a way that is usable and reachable by people with accessibility needs.
-
E.
transferAgreement
Indicates a formal arrangement in which ownership, rights, or responsibilities are transferred from one party to another.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: May 3, 2026, 4:09 p.m.