Triple
T37661324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | zoglin |
E937723
|
entity |
| Predicate | behaviorType |
P183170
|
FINISHED |
| Object | hostile to most mobs |
—
|
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: hostile to most mobs | Statement: [zoglin, behaviorType, hostile to most mobs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: behaviorType Context triple: [zoglin, behaviorType, hostile to most mobs]
-
A.
behaviorDescription
chosen
Indicates a textual explanation or characterization of how an entity behaves or acts in a given context.
-
B.
behaviorCode
Indicates the specific rule, standard, or classification code that governs or characterizes an entity’s behavior in a given context.
-
C.
behaviorObserved
Indicates that a particular behavior or action has been witnessed, recorded, or detected in relation to an entity or context.
-
D.
behaviorNear
Indicates that one entity exhibits a behavior or action in close spatial proximity to another entity.
-
E.
privateBehavior
Indicates behavior or actions that are intended to be kept confidential, hidden, or restricted from public or general observation.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.