Triple
T31068814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walter |
E791755
|
entity |
| Predicate | hasPhysicalAppearance |
P31173
|
FINISHED |
| Object | resembles David 8 |
—
|
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: resembles David 8 | Statement: [Walter, hasPhysicalAppearance, resembles David 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalAppearance Context triple: [Walter, hasPhysicalAppearance, resembles David 8]
-
A.
hasCharacterAppearance
Indicates that a character appears or is visually represented within a given work, scene, or context.
-
B.
hasPhysicalFeature
chosen
Indicates that one entity possesses or exhibits a specific physical characteristic or feature of another entity.
-
C.
hasLifeAppearance
Indicates that one entity exhibits the visual or observable characteristics typically associated with being alive.
-
D.
describesAppearanceOf
Indicates that one entity provides information about the visual characteristics or outward look of another entity.
-
E.
hasHumanCharacteristic
Indicates that an entity possesses a trait, quality, or behavior typically associated with humans.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 29, 2026, 9:01 p.m.