Triple
T30620763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCAS |
E779437
|
entity |
| Predicate | applicationSystem |
P148351
|
FINISHED |
| Object | online application portal |
—
|
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: online application portal | Statement: [UCAS, applicationSystem, online application portal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicationSystem Context triple: [UCAS, applicationSystem, online application portal]
-
A.
applicationTool
Indicates that one entity is a tool or instrument used to apply, operate, or carry out the function of another entity.
-
B.
applicationInterface
Indicates that one entity serves as an interface or interaction layer through which another entity accesses or uses an application’s functionality.
-
C.
softwareSystem
chosen
Indicates a relationship where an entity functions as, or is classified as, a software system.
-
D.
applicationRequirement
Indicates that one entity specifies a condition or prerequisite that must be met for the use, approval, or execution of another entity or process.
-
E.
aplicación
Indicates that one entity is the use or implementation of another entity for a specific purpose or function.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: April 29, 2026, 8:27 p.m.