Triple
T2836616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Worldwide Developers Conference 2006 |
E62366
|
entity |
| Predicate | hasLabs |
P15417
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Apple Worldwide Developers Conference 2006, hasLabs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLabs Context triple: [Apple Worldwide Developers Conference 2006, hasLabs, yes]
-
A.
laboratoryModule
Indicates a relationship where an entity is a laboratory module or functions as a lab-specific component or unit within a larger system or structure.
-
B.
hasResearchInfrastructure
chosen
Indicates that an entity possesses, controls, or provides access to facilities, equipment, or resources used to conduct research.
-
C.
hasResearchActivities
Indicates that an entity engages in, conducts, or is associated with research-related activities.
-
D.
hasResearchUse
Indicates that an entity is used for, or associated with, conducting research activities or purposes.
-
E.
experimentedOn
Indicates that one entity conducted experiments or tests on another entity as the subject of investigation.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdeec60a08190b76b52042713d647 |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.