Triple
T27664012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codelabs |
E697186
|
entity |
| Predicate | oftenFeaturedAt |
P175980
|
FINISHED |
| Object | developer conferences |
—
|
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: developer conferences | Statement: [Codelabs, oftenFeaturedAt, developer conferences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenFeaturedAt Context triple: [Codelabs, oftenFeaturedAt, developer conferences]
-
A.
featuredOn
Indicates that one entity is prominently presented, highlighted, or showcased on or within another entity (such as a platform, publication, or product).
-
B.
alsoFeatured
Indicates that an entity appears in addition to another primary entity within the same context, work, or presentation.
-
C.
featuredIn
Indicates that one entity appears or is prominently included within another entity, such as a person, work, or item being showcased in a larger work, event, or context.
-
D.
laterFeaturedIn
Indicates that an entity was featured or highlighted at a later time in another work, context, or medium.
-
E.
featuredFor
Indicates that one entity is highlighted, promoted, or specially showcased in the context or for the benefit of another entity.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 27, 2026, 2:37 p.m.