Triple
T3001164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halcyon days |
E81189
|
entity |
| Predicate | commonCollocation |
P44966
|
FINISHED |
| Object | "the halcyon days of youth" |
—
|
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: "the halcyon days of youth" | Statement: [Halcyon days, commonCollocation, "the halcyon days of youth"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonCollocation Context triple: [Halcyon days, commonCollocation, "the halcyon days of youth"]
-
A.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
B.
moreCommonIn
Indicates that something occurs with greater frequency or prevalence in one group, context, or location than in another.
-
C.
collocatedWith
Indicates that two entities are located in the same place or spatial context at the same time.
-
D.
sharesSpellingWith
Indicates that two entities have identical or substantially identical written forms (i.e., they are spelled the same way).
-
E.
commonFor
Indicates that something is typical, usual, or frequently occurring for a given entity or context.
- F. None of above. chosen
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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a1022e48190afee77db94635ff2 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 2:59 p.m.