Triple
T14529410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brently Mallard |
E340863
|
entity |
| Predicate | hasCharacterization |
P662
|
FINISHED |
| Object | seemingly loving |
—
|
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: seemingly loving | Statement: [Brently Mallard, hasCharacterization, seemingly loving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacterization Context triple: [Brently Mallard, hasCharacterization, seemingly loving]
-
A.
resultCharacterization
Indicates how the outcome of an event, process, or action is qualitatively described or characterized.
-
B.
findingCharacterization
Indicates that a finding is being described or classified in terms of its nature, features, or diagnostic significance.
-
C.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
D.
initialCharacterization
Indicates the first or earliest formal description, assessment, or classification made about an entity or situation.
-
E.
ruleCharacterization
Indicates that one rule is described, defined, or characterized in terms of another rule or set of rules.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea051bc608190ad4d516c5e7bca43 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.