Triple
T37709244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torna Fort |
E939279
|
entity |
| Predicate | connectedToFort |
P37306
|
FINISHED |
| Object | Rajgad Fort |
—
|
NE NERFINISHED |
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: Rajgad Fort | Statement: [Torna Fort, connectedToFort, Rajgad Fort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToFort Context triple: [Torna Fort, connectedToFort, Rajgad Fort]
-
A.
connectedToField
Indicates that one entity has a direct link, association, or attachment to a specific field within a structure, system, or dataset.
-
B.
connectionTo
chosen
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
C.
reportedConnection
Indicates that a relationship or link between entities has been asserted or documented by some source, but may not be independently verified.
-
D.
connectedToOrganization
Indicates that an entity has a relationship or association with a particular organization, such as membership, affiliation, or formal linkage.
-
E.
connectsBeyond
Indicates a relationship where one entity forms a link or association that extends past a usual boundary, scope, or intermediary to reach another entity.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffff262fac8190a26ed0577e1860bd |
completed | May 10, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69fffcad7d7c8190a4ad7bb35e33bb75 |
completed | May 10, 2026, 3:34 a.m. |
Created at: May 3, 2026, 4:18 p.m.