Triple
T38200574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Ones |
E1009042
|
entity |
| Predicate | featuresHitsFrom |
P137976
|
FINISHED |
| Object | Permanent Vacation |
E308754
|
NE 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: Permanent Vacation | Statement: [Big Ones, featuresHitsFrom, Permanent Vacation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresHitsFrom Context triple: [Big Ones, featuresHitsFrom, Permanent Vacation]
-
A.
includesHits
chosen
Indicates that one entity contains or encompasses one or more hits, results, or matching items associated with another entity.
-
B.
hits
Indicates a physical impact where one entity forcefully strikes or makes contact with another.
-
C.
ALHits
Indicates that a baseball player achieved a hit while playing in an American League (AL) game.
-
D.
featuresGreatestHits
Indicates that an entity (such as a media item, collection, or product) includes or highlights a selection of the most popular or successful works associated with another entity.
-
E.
producedHitFor
Indicates that one entity created or contributed to a successful or popular work (a "hit") for another entity.
- F. None of above.
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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a417b4af6948190896737c6d61f2e4d |
completed | June 28, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.