Triple
T7883513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ross Volunteers |
E183040
|
entity |
| Predicate | serviceBranchTradition |
P18685
|
FINISHED |
| Object | Army-style corps of cadets tradition |
—
|
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: Army-style corps of cadets tradition | Statement: [Ross Volunteers, serviceBranchTradition, Army-style corps of cadets tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceBranchTradition Context triple: [Ross Volunteers, serviceBranchTradition, Army-style corps of cadets tradition]
-
A.
servesTradition
Indicates that one entity upholds, maintains, or performs a tradition for the benefit or continuation of that tradition.
-
B.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
C.
traditionsMaintainedBy
chosen
Indicates that certain traditions are preserved, upheld, or continued in practice by a particular entity.
-
D.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
-
E.
describesTradition
Indicates that one entity explains, details, or characterizes a particular tradition 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_69ca828af6e48190a06ee7010d8f0e64 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39d36574819092d70e24c37952d7 |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:58 p.m.