Triple
T5513084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean Zay |
E144612
|
entity |
| Predicate | accessibleThrough |
P41137
|
FINISHED |
| Object | peer-reviewed project proposals |
—
|
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: peer-reviewed project proposals | Statement: [Jean Zay, accessibleThrough, peer-reviewed project proposals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessibleThrough Context triple: [Jean Zay, accessibleThrough, peer-reviewed project proposals]
-
A.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
B.
accessibleOn
Indicates that one entity can be reached, used, or obtained through another entity (such as a platform, device, or medium).
-
C.
accessibleAs
Indicates that one entity can be reached, used, or obtained through another entity, often as an alternative form, route, or representation.
-
D.
accessedThrough
chosen
Indicates that one entity is reached, used, or obtained by means of another entity that serves as an intermediary channel, tool, or pathway.
-
E.
areAccessibleAt
Indicates that certain entities can be reached, used, or entered at a specified location, time, 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_69c008f77ff88190b0cd50ca207295d1 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f599d0881909ce86fcc45d4d920 |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.