Triple
T36978334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilot Custom |
E914755
|
entity |
| Predicate | writingExperience |
P187240
|
FINISHED |
| Object | smooth |
—
|
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: smooth | Statement: [Pilot Custom, writingExperience, smooth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingExperience Context triple: [Pilot Custom, writingExperience, smooth]
-
A.
writtenAgainst
Indicates that a written work (such as a document, article, or statement) is composed in opposition to, or as a critique or complaint about, a particular target.
-
B.
writingComponent
Indicates that one entity is a written part or element that contributes to the composition or structure of another entity.
-
C.
writingCommunity
Indicates a relationship where individuals participate in or belong to a group centered around writing activities, collaboration, or shared literary interests.
-
D.
wrote
Indicates that an entity is the author or creator of a written work involving another entity.
-
E.
writingModel
Indicates that one entity serves as the writing system, script, or notation model used to represent the language or written content of another entity.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb34e4906c8190abb1c293fb84329a |
completed | May 6, 2026, 12:32 p.m. |
Created at: May 3, 2026, 4:14 p.m.