Triple
T15368818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Full Frontal |
E367487
|
entity |
| Predicate | featuresFormatElement |
P9789
|
FINISHED |
| Object | recurring characters |
—
|
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: recurring characters | Statement: [Full Frontal, featuresFormatElement, recurring characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresFormatElement Context triple: [Full Frontal, featuresFormatElement, recurring characters]
-
A.
featuresFormat
Indicates that something (such as a product, service, or medium) is presented, delivered, or made available in a particular format or configuration.
-
B.
formsFeature
chosen
Indicates that one entity constitutes or creates a characteristic, component, or distinguishing element of another entity.
-
C.
featuresStructure
Indicates that one entity possesses, exhibits, or incorporates a particular structure as a notable characteristic or component.
-
D.
featureSet
Indicates that one entity is a collection or configuration of features associated with or applied to another entity.
-
E.
featuresText
Indicates that an entity includes or presents a specific piece of text as one of its characteristics or contents.
- F. None of above.
Provenance (3 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e4b88a881909f9575c02aed287d |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca9ab7e88190a9261ef27be665b1 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.