Triple
T25145405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wayebʼ |
E629919
|
entity |
| Predicate | behaviorDuringPeriod |
P123846
|
FINISHED |
| Object | avoidance of certain activities |
—
|
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: avoidance of certain activities | Statement: [Wayebʼ, behaviorDuringPeriod, avoidance of certain activities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: behaviorDuringPeriod Context triple: [Wayebʼ, behaviorDuringPeriod, avoidance of certain activities]
-
A.
functionDuringPeriod
Indicates that a function, role, or activity is performed or valid throughout a specified time period.
-
B.
appliedDuringPeriod
chosen
Indicates that an action, condition, or status was in effect throughout a specified time period.
-
C.
rulesDuring
Indicates that one entity holds authority or governance over another throughout a specified time period or interval.
-
D.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
E.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4684c76048190bc6e4273d00aaceb |
completed | May 1, 2026, 8:46 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:29 a.m.