Triple
T37924071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewes Brooks |
E946041
|
entity |
| Predicate | typicalManagement |
P184581
|
FINISHED |
| Object | livestock grazing |
—
|
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: livestock grazing | Statement: [Lewes Brooks, typicalManagement, livestock grazing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalManagement Context triple: [Lewes Brooks, typicalManagement, livestock grazing]
-
A.
managementIs
Indicates that one entity holds a managerial role, responsibility, or authority over another entity.
-
B.
traditionalManagement
chosen
Indicates that an entity manages or governs another entity using long-established, conventional methods, structures, or practices rather than modern or innovative approaches.
-
C.
manageThrough
Indicates that one entity exercises control, direction, or administration over another entity or process by means of an intermediary entity, channel, or mechanism.
-
D.
managementUse
Indicates that one entity uses or employs another entity specifically for management or administrative purposes.
-
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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.