Triple
T9395270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jet |
E226126
|
entity |
| Predicate | hasChartingStatus |
P62296
|
FINISHED |
| Object | hit single |
—
|
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: hit single | Statement: [Jet, hasChartingStatus, hit single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChartingStatus Context triple: [Jet, hasChartingStatus, hit single]
-
A.
hasCharting
Indicates that one entity provides or supports charting or graphical data visualization capabilities for another entity.
-
B.
chartStatus
chosen
Indicates the current state or condition of a chart, such as whether it is active, updated, or in a particular workflow stage.
-
C.
hasChartedIn
Indicates that something (such as a song, album, or work) has appeared on an official ranking or popularity chart within a specified context (such as a country, chart type, or time period).
-
D.
hasChartingCover
Indicates that one entity serves as the charting or graphical representation (cover) of another entity’s data or content.
-
E.
isChartedOn
Indicates that something is represented or plotted on a particular chart or graph.
- 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_69ca842f7e3481908bf5bcf52e032dbd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5112faa08190a8dd2c461d1e7a14 |
completed | April 1, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:45 p.m.