Triple
T582945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Military College, Duntroon |
E15095
|
entity |
| Predicate | hasIntake |
P13353
|
FINISHED |
| Object | Australian officer cadets |
—
|
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: Australian officer cadets | Statement: [Royal Military College, Duntroon, hasIntake, Australian officer cadets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntake Context triple: [Royal Military College, Duntroon, hasIntake, Australian officer cadets]
-
A.
hasReception
Indicates that an entity hosts, includes, or is associated with a reception event (such as a formal gathering or welcoming function).
-
B.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
C.
primaryIntake
chosen
Indicates that one entity serves as the main or first point of intake, reception, or admission for another entity.
-
D.
canIntroduce
Indicates that one entity has the ability or permission to introduce another entity to a third party or context.
-
E.
hasStand
Indicates that an entity possesses, is equipped with, or is supported by a stand or base structure.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b85becc8190b4d98c00e5fa7c04 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c9315c8190a773e8e00737d8a0 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.