Triple
T4795281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajanta Caves |
E106694
|
entity |
| Predicate | discoveredByOccupation |
P412
|
FINISHED |
| Object | British officer |
—
|
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: British officer | Statement: [Ajanta Caves, discoveredByOccupation, British officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredByOccupation Context triple: [Ajanta Caves, discoveredByOccupation, British officer]
-
A.
discoveredBy
chosen
Indicates that something was found, identified, or brought to light through the efforts or actions of a particular agent.
-
B.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
C.
foundedByOccupation
Indicates that an entity (such as an organization or institution) was founded by a person or group characterized by a specific occupation or professional role.
-
D.
co-discoveredWith
Indicates that two or more entities jointly discovered the same object, phenomenon, or finding.
-
E.
derivesFromOccupation
Indicates that one entity originates from, is obtained through, or is a result of another entity’s occupation or professional role.
- 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6b40c29c8190adab3503f8ba0145 |
completed | March 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69bd622f88188190a51d52ccfad3d2dd |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.