Triple
T34240734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cnicht |
E878455
|
entity |
| Predicate | hasPhotogenicProfileFrom |
P181796
|
FINISHED |
| Object | Porthmadog |
—
|
NE NERFINISHED |
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: Porthmadog | Statement: [Cnicht, hasPhotogenicProfileFrom, Porthmadog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhotogenicProfileFrom Context triple: [Cnicht, hasPhotogenicProfileFrom, Porthmadog]
-
A.
hasPhotoOn
Indicates that one entity has an associated photograph stored, displayed, or linked on another entity (such as a platform, page, or medium).
-
B.
hasPhotographBy
Indicates that an entity is depicted in or associated with a photograph that was created or taken by a specified photographer.
-
C.
hasPhotogenicFeature
Indicates that an entity possesses a visual characteristic or attribute that is especially attractive or appealing when photographed.
-
D.
hasPhotograph
Indicates that one entity possesses, includes, or is associated with a photograph depicting or representing another entity.
-
E.
hasPhotographAt
Indicates that a photograph depicting an entity was taken or exists at a specific location or event.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: May 1, 2026, 1:56 a.m.