Triple
T27102218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sankara Stones |
E686471
|
entity |
| Predicate | numberRecoveredByIndianaJones |
P197290
|
FINISHED |
| Object | three |
—
|
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: three | Statement: [Sankara Stones, numberRecoveredByIndianaJones, three]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberRecoveredByIndianaJones Context triple: [Sankara Stones, numberRecoveredByIndianaJones, three]
-
A.
numberOfBonesRecovered
Indicates the count of bones that have been found and recovered in relation to a particular subject or event.
-
B.
treasureInvolved
Indicates that a situation, event, or action involves or is related to treasure in some significant way.
-
C.
nationalTreasureNumber
Indicates that an entity is assigned a specific official national treasure identification number within a country’s heritage or cultural registry.
-
D.
rescuedDuring
Indicates that one entity was rescued in the course of, or as part of, a specified event or time period.
-
E.
recoveredIn
Indicates that something lost, damaged, or impaired has been restored or regained within a particular context, process, or location.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
| PDg | Predicate description generation | batch_69fe86c98d688190a99d5dcb14e2dc95 |
completed | May 9, 2026, 12:58 a.m. |
Created at: April 27, 2026, 8:48 a.m.