Triple
T12376029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BR |
E295123
|
entity |
| Predicate | hasPrefixRole |
P55388
|
FINISHED |
| Object | prefix for numeric RTO codes in Bihar |
—
|
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: prefix for numeric RTO codes in Bihar | Statement: [BR, hasPrefixRole, prefix for numeric RTO codes in Bihar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrefixRole Context triple: [BR, hasPrefixRole, prefix for numeric RTO codes in Bihar]
-
A.
hasPrefix
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
B.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
C.
hasEarlyRoleFor
Indicates that one entity holds or performs an initial or early-stage role in relation to another entity or process.
-
D.
hasRelativeRole
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
-
E.
hasCallsignPrefixRole
chosen
Indicates that an entity has a specific role associated with a given callsign prefix.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93fb8d6c081909e8bbbd52c73f29c |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.