Triple
T24706409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prajapatis |
E611903
|
entity |
| Predicate | linkedWithConcept |
P531
|
FINISHED |
| Object | sacrifice as creative act |
—
|
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: sacrifice as creative act | Statement: [Prajapatis, linkedWithConcept, sacrifice as creative act]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedWithConcept Context triple: [Prajapatis, linkedWithConcept, sacrifice as creative act]
-
A.
linkedByStructure
Indicates that two entities are connected or associated through a shared structural element, configuration, or framework.
-
B.
hasConceptualInvolvementBy
Indicates that something is conceptually influenced, shaped, or defined by the ideas, theories, or mental contributions of a particular agent or source.
-
C.
hasConcept
chosen
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
D.
linkedToProperty
Indicates that one entity is associated or connected to a specific property or attribute of another entity.
-
E.
commonlyLinkedTo
Indicates that one entity is frequently or typically associated, connected, or co-occurring with 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 3:24 a.m.