Triple
T35842904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Fravor |
E1036133
|
entity |
| Predicate | describedObjectShapeAs |
P143336
|
FINISHED |
| Object | white Tic Tac shaped with no visible control surfaces |
—
|
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: white Tic Tac shaped with no visible control surfaces | Statement: [David Fravor, describedObjectShapeAs, white Tic Tac shaped with no visible control surfaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedObjectShapeAs Context triple: [David Fravor, describedObjectShapeAs, white Tic Tac shaped with no visible control surfaces]
-
A.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
-
B.
SHAPEObjective
Indicates a relationship where an entity serves as the goal or intended outcome within the SHAPE framework or process.
-
C.
shape
Indicates that one entity has a particular geometric or physical form characterized by the other entity.
-
D.
describesAppearanceOf
chosen
Indicates that one entity provides information about the visual characteristics or outward look of another entity.
-
E.
shapeType
Indicates the specific geometric form or category that characterizes an entity’s shape.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 3, 2026, 4:06 p.m.