Triple
T25782121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Entrance Examination |
E649317
|
entity |
| Predicate | typicalEntryPoint |
P26093
|
FINISHED |
| Object | Year 9 |
—
|
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: Year 9 | Statement: [Common Entrance Examination, typicalEntryPoint, Year 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEntryPoint Context triple: [Common Entrance Examination, typicalEntryPoint, Year 9]
-
A.
typicalEntryFile
Indicates that a given file is the standard or primary entry point typically used to start or access something (such as a program, project, or package).
-
B.
entryPointFor
chosen
Indicates that one entity serves as the access or starting location through which another entity is entered, initiated, or reached.
-
C.
typicalEntryRoute
Indicates the usual or most common path or method by which something is entered or accessed.
-
D.
isCommonEntryPointFor
Indicates that something serves as a shared or frequently used starting location or access point for multiple entities or processes.
-
E.
typicalEntryPointDepth
Indicates the usual or characteristic depth at which an entry point occurs or is established.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: April 22, 2026, 5:51 a.m.