Triple
T31930706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beautiful Girl |
E815239
|
entity |
| Predicate | hasTitleOnRelease |
P192504
|
FINISHED |
| Object | Beautiful Girl |
—
|
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: Beautiful Girl | Statement: [Beautiful Girl, hasTitleOnRelease, Beautiful Girl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleOnRelease Context triple: [Beautiful Girl, hasTitleOnRelease, Beautiful Girl]
-
A.
hasTitleSince
Indicates that an entity has held a particular title continuously starting from a specified point in time.
-
B.
hasTitleOf
Indicates that one entity holds, bears, or is designated by the official title, name, or rank specified by another entity.
-
C.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
D.
hasTitleOver
Indicates that one entity holds a formal title, rank, or designation in relation to another entity.
-
E.
hasTitleFeature
Indicates that an entity possesses a specific characteristic, attribute, or element related to its title.
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69fd0d0aebac8190868a7714ddb4f1fd |
completed | May 7, 2026, 10:07 p.m. |
Created at: May 1, 2026, 12:04 a.m.