Triple
T29842722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rigaudon |
E757844
|
entity |
| Predicate | phraseStructure |
P4412
|
FINISHED |
| Object | four-bar phrases |
—
|
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: four-bar phrases | Statement: [Rigaudon, phraseStructure, four-bar phrases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phraseStructure Context triple: [Rigaudon, phraseStructure, four-bar phrases]
-
A.
grammaticalStructure
chosen
Indicates the way linguistic elements are organized and related within a sentence or phrase according to grammatical rules.
-
B.
positionStructure
Indicates a spatial or organizational arrangement relationship, specifying how one structure is positioned or configured relative to another.
-
C.
branchStructure
Indicates how the parts of a branching system are organized and connected relative to one another.
-
D.
segmentStructure
Indicates that one entity represents a structural or organizational subdivision (a segment) within the overall structure of another entity.
-
E.
sentenceType
Indicates the classification of a sentence according to its communicative function or structural type (e.g., question, statement, command).
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6760b3d6081909d0e3748483989a4 |
completed | May 2, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:40 p.m.