Triple
T33019226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aazhi Ther |
E844858
|
entity |
| Predicate | isPulledThrough |
P10351
|
FINISHED |
| Object | streets of Tiruvarur |
—
|
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: streets of Tiruvarur | Statement: [Aazhi Ther, isPulledThrough, streets of Tiruvarur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPulledThrough Context triple: [Aazhi Ther, isPulledThrough, streets of Tiruvarur]
-
A.
pulledBy
chosen
Indicates that one entity is moved or drawn by the force or action exerted by another entity.
-
B.
canBePulledBackAlong
Indicates that a structure or object can be transferred or redefined along a given mapping or morphism so that it is compatible with that mapping.
-
C.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
D.
ownedThrough
Indicates that one entity possesses or controls another indirectly via an intermediate entity, structure, or arrangement (such as a subsidiary, trust, or other vehicle).
-
E.
passesUnder
Indicates that one entity moves or extends beneath another entity, typically crossing below it without direct contact.
- 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:23 a.m.