Triple
T10026990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People’s Place |
E200755
|
entity |
| Predicate | launchPadFor |
P53971
|
FINISHED |
| Object | Tommy Hilfiger’s fashion career |
—
|
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: Tommy Hilfiger’s fashion career | Statement: [People’s Place, launchPadFor, Tommy Hilfiger’s fashion career]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchPadFor Context triple: [People’s Place, launchPadFor, Tommy Hilfiger’s fashion career]
-
A.
launchPad
Indicates a physical platform or site from which vehicles, typically rockets or spacecraft, are launched.
-
B.
controlsLaunchPad
Indicates that one entity has the authority or capability to manage, operate, or direct the use of a launch pad.
-
C.
launchProvider
Indicates that one entity serves as the organization or company responsible for launching another entity (such as a spacecraft, satellite, or mission).
-
D.
launchPlatformFor
chosen
Indicates a relationship where one entity serves as the platform or site from which another entity is launched.
-
E.
launchDestination
Indicates the target location or endpoint toward which something is launched or sent.
- 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcde3c1b88190924e6158f406b453 |
completed | April 2, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:54 p.m.