Triple
T4087407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coalition Application |
E87620
|
entity |
| Predicate | applicationLevel |
P39730
|
FINISHED |
| Object | undergraduate |
—
|
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: undergraduate | Statement: [Coalition Application, applicationLevel, undergraduate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicationLevel Context triple: [Coalition Application, applicationLevel, undergraduate]
-
A.
applicationLayerProtocol
Indicates that one entity uses, implements, or is associated with a specific application-layer communication protocol in a networked interaction.
-
B.
typeOfApplication
Indicates the specific category or kind of application involved in the relationship or action.
-
C.
applicationRequirement
chosen
Indicates that one entity specifies a condition or prerequisite that must be met for the use, approval, or execution of another entity or process.
-
D.
automationLevel
Indicates the degree to which a process, task, or system is performed automatically rather than manually.
-
E.
definesApplication
Indicates that one entity specifies or establishes the purpose, scope, or behavior of an application associated with another entity.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefca899008190b5ada98bdb79639f |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.