Triple
T28298729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reprise |
E713642
|
entity |
| Predicate | featuresCrossoverStyle |
P196862
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Reprise, featuresCrossoverStyle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCrossoverStyle Context triple: [Reprise, featuresCrossoverStyle, true]
-
A.
featuresCrossoverWith
Indicates that one entity includes or participates in a crossover event or collaboration with another entity.
-
B.
featuresCross
Indicates that one feature or element intersects or passes across another in space or structure.
-
C.
crossingStyle
Indicates the manner or method by which one entity crosses or traverses another (such as a boundary, path, or medium).
-
D.
featuresCrossShape
Indicates that something has a form, pattern, or configuration resembling a cross shape.
-
E.
crossStyle
Indicates the manner or style in which something or someone crosses from one side, path, or medium to another.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fe6c7fc4388190aa88993d00872d7f |
completed | May 8, 2026, 11:06 p.m. |
Created at: April 27, 2026, 11:34 p.m.