Triple
T15004500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | administration of Akbar |
E377673
|
entity |
| Predicate | requiredPractice |
P100
|
FINISHED |
| Object | dagh system of branding horses |
—
|
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: dagh system of branding horses | Statement: [administration of Akbar, requiredPractice, dagh system of branding horses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredPractice Context triple: [administration of Akbar, requiredPractice, dagh system of branding horses]
-
A.
requiresPractice
Indicates that performing or mastering one entity depends on engaging in repeated practice or training involving another entity.
-
B.
endedPracticeOf
Indicates that one entity caused another entity to stop or discontinue a particular practice or activity.
-
C.
supportedPractice
Indicates that one entity endorses, promotes, or facilitates the use of a particular practice by another entity.
-
D.
requires
chosen
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
E.
mentionsPractice
Indicates that one entity refers to, discusses, or brings up a particular practice in some form of communication.
- 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_69ded7322b5c81909089cbbf816e1436 |
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:54 a.m.