Triple
T5348055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Take the "A" Train |
E124103
|
entity |
| Predicate | isFrequentlyUsedAs |
P46711
|
FINISHED |
| Object | opening number in jazz concerts |
—
|
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: opening number in jazz concerts | Statement: [Take the "A" Train, isFrequentlyUsedAs, opening number in jazz concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFrequentlyUsedAs Context triple: [Take the "A" Train, isFrequentlyUsedAs, opening number in jazz concerts]
-
A.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
-
B.
isFrequentlyIncludedIn
chosen
Indicates that something is regularly or commonly contained or made part of something else.
-
C.
isFrequentlyPerformedBy
Indicates that an action or activity is carried out often or on a regular basis by a particular entity.
-
D.
isFamouslyUsedIn
Indicates that something is widely recognized or well-known for being used in a particular context, work, or situation.
-
E.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
- 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85ef75148190815461c2a49302e9 |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.