Triple
T18320721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exaggerator |
E438869
|
entity |
| Predicate | hasSurfacePreference |
P131373
|
FINISHED |
| Object | dirt |
—
|
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: dirt | Statement: [Exaggerator, hasSurfacePreference, dirt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfacePreference Context triple: [Exaggerator, hasSurfacePreference, dirt]
-
A.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
-
B.
hasSurfaceFeatureState
Indicates that an entity currently exhibits a particular condition or status of one of its surface features.
-
C.
hasSurfaceLevel
Indicates that one entity possesses or is characterized by a particular degree or measure of surface level (e.g., depth, detail, or superficiality).
-
D.
usesSurface
Indicates that one entity employs or interacts with another entity as a surface or platform for its action or function.
-
E.
hasSurfaceActivity
Indicates that an entity exhibits measurable physical or chemical activity occurring at or on its surface.
- F. None of above. chosen
Provenance (4 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa5a3508190a3025e71c11d79e2 |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:36 a.m.