Triple
T567834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star user interface |
E13593
|
entity |
| Predicate | primaryMetaphor |
P15665
|
FINISHED |
| Object | office desktop |
—
|
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: office desktop | Statement: [Star user interface, primaryMetaphor, office desktop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMetaphor Context triple: [Star user interface, primaryMetaphor, office desktop]
-
A.
primaryMotif
Indicates that one entity serves as the main recurring theme or dominant motif associated with another entity.
-
B.
primarySense
Indicates that one sense or meaning of an entity is designated as its main or most central sense among possible alternatives.
-
C.
primaryMode
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
-
D.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
-
E.
primaryAlignment
Indicates the main or most significant way in which one entity is aligned, associated, or in agreement with another entity, standard, or category.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b02da148190b6a9bad3a22d8ec5 |
completed | March 1, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69a494c183b081909304944aa3d0fe8f |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985a2d08819090947895d9439e06 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.