Triple
T19864167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atik (ancient) |
E477343
|
entity |
| Predicate | relationshipToArichAnpin |
P137616
|
FINISHED |
| Object | inner essence of Arich Anpin |
—
|
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: inner essence of Arich Anpin | Statement: [Atik (ancient), relationshipToArichAnpin, inner essence of Arich Anpin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToArichAnpin Context triple: [Atik (ancient), relationshipToArichAnpin, inner essence of Arich Anpin]
-
A.
relationshipToRa
Indicates a specified type of relational connection that an entity has to the entity Ra.
-
B.
relationshipToARP
Indicates a specified type of relationship or association that an entity has to an ARP (which may represent a particular person, program, plan, or reference point).
-
C.
relationshipToVillagers
Indicates the nature or type of relationship that an entity has with the villagers.
-
D.
relationshipToTopa
Indicates a familial or social relationship that an entity has specifically with Topa.
-
E.
relationshipToNationalTreasures
Indicates a specified type of connection or association that an entity has with designated national treasures.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6589d55a88190af7d4e12c4b07739 |
completed | April 20, 2026, 4:47 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:51 p.m.