Triple
T15009336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Military Course |
E377792
|
entity |
| Predicate | typicalEntryLevel |
P90637
|
FINISHED |
| Object | freshman college students |
—
|
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: freshman college students | Statement: [General Military Course, typicalEntryLevel, freshman college students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEntryLevel Context triple: [General Military Course, typicalEntryLevel, freshman college students]
-
A.
typicalExperienceLevel
chosen
Indicates the usual or most common level of experience associated with an entity in a given context.
-
B.
typicalLowestLevel
Indicates that something represents the most basic or minimal level that is commonly or normally found within a given context.
-
C.
typicalIntermediateLevel
Indicates that something represents a common or standard degree of difficulty, complexity, or proficiency that falls between beginner and advanced levels.
-
D.
typicalEntryType
Indicates the usual or standard category or kind of entry associated with something.
-
E.
typicalSeniorityLevel
Indicates the usual or most common rank or seniority level associated with an entity in a given context.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded734943481908dad4ceed4fe850c |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:55 a.m.