Triple
T11659032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enderman |
E277076
|
entity |
| Predicate | AIBehavior |
P100765
|
FINISHED |
| Object | avoids water |
—
|
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: avoids water | Statement: [Enderman, AIBehavior, avoids water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AIBehavior Context triple: [Enderman, AIBehavior, avoids water]
-
A.
aiBehavior
chosen
Indicates how an artificial intelligence system acts or responds under given conditions or stimuli.
-
B.
behaviorCode
Indicates the specific rule, standard, or classification code that governs or characterizes an entity’s behavior in a given context.
-
C.
definingBehavior
Indicates the characteristic action or pattern of actions that fundamentally determines or typifies how something functions or is understood.
-
D.
shapesBehaviorOf
Indicates that one entity influences, determines, or constrains the way another entity behaves or acts.
-
E.
spaceBehavior
Indicates how an entity behaves, operates, or is arranged within a given space or spatial context.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
Created at: April 8, 2026, 9:39 p.m.