Triple
T24200697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mrs. Paddy |
E599968
|
entity |
| Predicate | hasDefiningBehavior |
P90665
|
FINISHED |
| Object | recites long lists of things she hates |
—
|
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: recites long lists of things she hates | Statement: [Mrs. Paddy, hasDefiningBehavior, recites long lists of things she hates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefiningBehavior Context triple: [Mrs. Paddy, hasDefiningBehavior, recites long lists of things she hates]
-
A.
definingBehavior
chosen
Indicates the characteristic action or pattern of actions that fundamentally determines or typifies how something functions or is understood.
-
B.
hasDefinition
Indicates that one entity provides the meaning, explanation, or definition of another entity.
-
C.
hasIRBehavior
Indicates that an entity exhibits or is characterized by a specific infrared (IR) behavior or response.
-
D.
hasCoreBehavior
Indicates that an entity possesses or exhibits a fundamental, defining behavior that is central to its function or identity.
-
E.
canBeDefinedFor
Indicates that a certain concept, operation, or property is applicable to and can be meaningfully specified for a given entity or set of entities.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca08874819081dd6613ac462c40 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.