Triple
T14299946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brumbies |
E354535
|
entity |
| Predicate | managementMethod |
P4839
|
FINISHED |
| Object | mustering |
—
|
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: mustering | Statement: [Brumbies, managementMethod, mustering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managementMethod Context triple: [Brumbies, managementMethod, mustering]
-
A.
managementIs
Indicates that one entity holds a managerial role, responsibility, or authority over another entity.
-
B.
manageThrough
Indicates that one entity exercises control, direction, or administration over another entity or process by means of an intermediary entity, channel, or mechanism.
-
C.
managementApproach
chosen
Indicates the strategy, methods, or style used to direct, organize, and oversee the activities or resources of an entity or process.
-
D.
managementController
Indicates that one entity serves as the management controller responsible for overseeing, configuring, or administering another entity.
-
E.
managerType
Indicates the specific category or role classification of a manager within an organizational or system 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de717e246c819083e67ac2b3b77881 |
completed | April 14, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:11 a.m.