Triple
T3453541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HP (vehicle registration code) |
E72847
|
entity |
| Predicate | followedByComponent |
P48313
|
FINISHED |
| Object | two-digit RTO code |
—
|
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: two-digit RTO code | Statement: [HP (vehicle registration code), followedByComponent, two-digit RTO code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByComponent Context triple: [HP (vehicle registration code), followedByComponent, two-digit RTO code]
-
A.
followedByTitle
Indicates that one title directly succeeds another in a sequence or ordered list.
-
B.
mayBeFollowedBy
Indicates that one event, state, or item is allowed or able to occur immediately after another in a sequence.
-
C.
followsFrom
Indicates that one fact, event, or state logically or causally results from, is implied by, or comes as a consequence of another.
-
D.
followedIn
Indicates that one entity began following or subscribing to another entity, typically in a social or sequential context.
-
E.
followedByStation
Indicates that one station directly succeeds another in a sequence, such as along a transit line or route.
- F. None of above. chosen
Provenance (4 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbaa457fc8190824ca00254e962f9 |
completed | March 8, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69adae041d588190a84a02bca94adec8 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:16 p.m.