Triple
T32283560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | eNeuro |
E824762
|
entity |
| Predicate | hasOnlineSubmissionSystem |
P131990
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [eNeuro, hasOnlineSubmissionSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlineSubmissionSystem Context triple: [eNeuro, hasOnlineSubmissionSystem, yes]
-
A.
hasOnlineForm
chosen
Indicates that an entity provides or is associated with a form that can be accessed and completed online.
-
B.
submissionSystem
Indicates a relationship where something is provided or turned in through a designated system or platform for receiving submissions.
-
C.
hasOnlineReception
Indicates that an entity provides or supports a reception, front-desk, or greeting function through online or digital channels rather than solely in person.
-
D.
hasOnlineRequirement
Indicates that an entity must be accessed, completed, or fulfilled through an online or internet-based component.
-
E.
hasOnlineCampus
Indicates that an institution or organization offers a campus or learning environment that is accessible via the internet.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, 12:43 a.m.