Triple
T24300797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unfiltered: Paris Jackson & Gabriel Glenn |
E606089
|
entity |
| Predicate | featuresRealLife |
P155472
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Unfiltered: Paris Jackson & Gabriel Glenn, featuresRealLife, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresRealLife Context triple: [Unfiltered: Paris Jackson & Gabriel Glenn, featuresRealLife, yes]
-
A.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
B.
featuresReimaginedVersionOf
Indicates that something includes or presents a newly interpreted or updated version of another existing work or element.
-
C.
featuresBuilding
Indicates that one entity includes or incorporates a building as a notable component or characteristic.
-
D.
featuresSituation
Indicates that a situation is characterized by, or has as one of its defining aspects, the specified feature or element.
-
E.
featuresSign
Indicates that an entity includes, displays, or incorporates a particular sign as part of its appearance, content, or design.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f2915e4ffc8190bf711dae443b3ec1 |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:09 a.m.