Triple
T2114931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honeycomb |
E42585
|
entity |
| Predicate | hasNotablePerformanceEra |
P561
|
FINISHED |
| Object | late 1950s |
—
|
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: late 1950s | Statement: [Honeycomb, hasNotablePerformanceEra, late 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePerformanceEra Context triple: [Honeycomb, hasNotablePerformanceEra, late 1950s]
-
A.
hasNotablePerformanceIn
Indicates that an entity delivered a significant or distinguished performance within a specified work, event, or context.
-
B.
notableEraNickname
Indicates the informal or popular nickname by which a particular historical era or period is commonly known.
-
C.
notableEra
chosen
Indicates the historical period or era for which an entity is especially recognized or significant.
-
D.
bestOfFiveEraStart
Indicates the point in time when a competition or series transitions into using a best-of-five format for its matches.
-
E.
hasNotablePlayer
Indicates that an entity (such as a team or club) is associated with a player who is particularly distinguished, famous, or significant in its context.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb0724e08190a0a4210d86261d6d |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.