Triple
T16286228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myrmecia |
E395393
|
entity |
| Predicate | aggressivenessTowardsHumans |
P101476
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Myrmecia, aggressivenessTowardsHumans, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aggressivenessTowardsHumans Context triple: [Myrmecia, aggressivenessTowardsHumans, high]
-
A.
aggressiveness
chosen
Indicates a tendency or disposition of an entity to initiate hostile, forceful, or confrontational actions toward others.
-
B.
describesAggressionAs
Indicates how one entity characterizes or portrays the aggression exhibited by another entity.
-
C.
violenceLevel
Indicates the degree or intensity of violent behavior, actions, or content present in or associated with an entity.
-
D.
treatsHumansAs
Indicates how one entity regards or behaves toward humans, characterizing them in a particular way (e.g., as equals, tools, resources, or threats).
-
E.
threatToHumans
Indicates that the subject poses or represents a potential danger, harm, or risk to humans.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24914bda08190a5d6315414ee3f76 |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.