Triple
T21079101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On Aggression |
E519312
|
entity |
| Predicate | appliesConceptTo |
P531
|
FINISHED |
| Object | human social behavior |
—
|
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: human social behavior | Statement: [On Aggression, appliesConceptTo, human social behavior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesConceptTo Context triple: [On Aggression, appliesConceptTo, human social behavior]
-
A.
hasConcept
chosen
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
B.
usesConceptIdentifier
Indicates that one entity refers to or operates with a specific concept by means of its unique identifier.
-
C.
exportsConcept
Indicates that one entity sends or supplies a concept, idea, or abstract knowledge resource from itself to another entity or context.
-
D.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
E.
demonstratedConcept
Indicates that an entity has shown, illustrated, or made evident a particular concept through example, explanation, or action.
- 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702d939e08190a37d7b7cc1872ad5 |
completed | April 21, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:49 p.m.