Triple
T32635274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarana-e-Milli |
E834328
|
entity |
| Predicate | lineTranslation |
P174752
|
FINISHED |
| Object | China and Arabia are ours, India is ours |
—
|
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: China and Arabia are ours, India is ours | Statement: [Tarana-e-Milli, lineTranslation, China and Arabia are ours, India is ours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineTranslation Context triple: [Tarana-e-Milli, lineTranslation, China and Arabia are ours, India is ours]
-
A.
lineUse
Indicates how a particular line (such as a route, track, or service line) is utilized or purposed within a system or network.
-
B.
lineConfiguration
Indicates that the entities participate together in a specific arrangement or pattern along a line.
-
C.
linePositioning
Indicates how one line is spatially arranged or oriented in relation to another line.
-
D.
linePositioning
Indicates the relative arrangement or alignment of elements along a line or linear sequence.
-
E.
lineReplaced
Indicates that one line has been substituted or superseded by another line, typically in a versioning, editing, or modification context.
- 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_69f3492dc2308190a88c6e30a3f3f576 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7e32ec08190b74856937c4a9fc3 |
completed | May 3, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:07 a.m.