Triple
T21989267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALEPH Collaboration |
E543040
|
entity |
| Predicate | languageOfScientificCommunication |
P77928
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [ALEPH Collaboration, languageOfScientificCommunication, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfScientificCommunication Context triple: [ALEPH Collaboration, languageOfScientificCommunication, English]
-
A.
hasPrimaryLanguageOfResearch
chosen
Indicates that an entity’s main or principal language used for conducting and publishing research is a specified language.
-
B.
citationLanguage
Indicates the language in which a cited work or reference is written or presented.
-
C.
roleInScholarlyCommunication
Indicates the function or position an entity holds within the processes of producing, evaluating, disseminating, or preserving scholarly work.
-
D.
languageOfSubmissions
Indicates the language in which the submissions are written or communicated.
-
E.
doctoralThesisLanguage
Indicates the language in which a doctoral thesis is written or formally presented.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1270cb67c81909a3aa2dc61c1894f |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:05 p.m.