Triple
T27358703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George |
E685756
|
entity |
| Predicate | hasFirstAppearanceWork |
P29367
|
FINISHED |
| Object | 27 Dresses |
E175864
|
NE 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: 27 Dresses | Statement: [George, hasFirstAppearanceWork, 27 Dresses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstAppearanceWork Context triple: [George, hasFirstAppearanceWork, 27 Dresses]
-
A.
firstAppearanceFor
chosen
Indicates that an entity marks the initial occurrence or debut of another entity within a given context or medium.
-
B.
workDateOfFirstAppearance
Indicates the date on which a work first appeared, was released, or was made publicly available.
-
C.
firstAppearedInWorkBy
Indicates that an entity made its first appearance within a specific work created by a particular author or creator.
-
D.
settingOfFirstAppearance
Indicates the location or context in which an entity is first introduced or appears.
-
E.
firstAppearsAs
Indicates that an entity is introduced or shown in a particular form, role, or identity for the first time in a given context.
- F. None of above.
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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12da6e066481909ed5abb3d4b20320 |
completed | May 24, 2026, 11:01 a.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 27, 2026, 11:52 a.m.